| title | sidebarTitle | og:description |
|---|---|---|
Customizing bank statement references |
Bank statements |
Send custom text to appear on the user’s bank statement for a payment on your platform. |
The Mangopay API allows you to customize the text that appears on the bank statement of an end user.
You can do this by sending custom text in specific parameters of the API (depending on the transaction and payment method). This is entirely optional, but it can help your end users to identify a transaction made on your platform.
The string of text that appears on the bank statement to describe a transaction contains, in order:
- A reference to Mangopay (e.g., MGP)
- Your platform’s trading name (as opposed to the legal registered name)
- Additional custom text that you can define
Because the 3 elements appear on one line of the bank statement, space is very limited and the custom text may be truncated.
It is possible for your platform to change its trading name to make it shorter, but this is controlled by Mangopay’s teams as part of its verification obligations.
**Note – Banks have ultimate control of the text displayed**Mangopay can supply a string of text for the bank statement but ultimately it is the user’s bank that decides if and how much of that information is displayed.
On pay-ins, platforms can use the StatementDescriptor parameter to send custom text (only alphanumeric characters or spaces).
The structure of the complete string sent is:
MGP*
TradingNameStatementDescriptor
On the following endpoints, the StatementDescriptor length is limited to 10 characters:
- Create a Direct Card PayIn
- Create a Web Card PayIn
- Create a Recurring PayIn (CIT)
- Create a Recurring PayIn (MIT)
- Create a Preauthorization
- Create a Deposit Preauthorization
- Create an Apple Pay PayIn
- Create a BLIK PayIn
- Create a Giropay PayIn
- Create a Google Pay PayIn
- Create an iDEAL PayIn
- Create a Klarna PayIn
- Create an MB WAY PayIn
- Create a Multibanco PayIn
- Create a PayPal PayIn
- Create a Satispay PayIn
For direct debits (on the Create a Direct Debit PayIn) the StatementDescriptor constraints differ depending on the Mandate scheme:
- BACS – The length is truncated after 10 characters
- SEPA – The length is limited to 100 characters
For SEPA Direct Debit pay-ins, the structure of the string sent is different:
StatementDescriptorTradingName
For refunds, the StatementDescriptor is only available on the direct debit payment method, both SEPA and BACS.
The length is limited to 10 characters (alphanumeric or spaces).
The string sent is only the parameter:
StatementDescriptor
On payouts, platforms can use the BankWireRef parameter to send custom text, including special characters.
The structure of the complete string sent is:
MGP*
TradingNameBankWireRef
On payouts, the recommended length is 12 characters. Strings longer than this may be truncated depending on the bank. The technical limit is 255 characters.