Overview
| Payment Type | SWIFT (Priority) | Local (Regular) |
|---|---|---|
| Cut off time (UK Time) | 2:00 pm | 2:00 pm |
| Delivery time frame | 1 day | 1 day |
| Maximum payment size | No limit | SGD 200,000 |
| Payment Scheme | SWIFT | FAST |
| Destination countries | Any (excluding sanctioned) | Singapore |
| Traces | Yes | No |
| Recalls | Yes | No |
| Ultimate payer displayed? | Yes | No |
Required Details
Local (Regular) Payment
| Field | Individual | Company | Permitted Data | Notes |
|---|---|---|---|---|
| Beneficiary Entity Type | ✓ | ✓ | ‘individual’ or ‘company’ only | |
| Beneficiary First Name | ✓ | ✕ | 1-255 characters* | |
| Beneficiary Last Name | ✓ | ✕ | 1-255 characters* | |
| Beneficiary Company Name | ✕ | ✓ | 1-255 characters* | |
| Beneficiary Address | ✓ | ✓ | 1-255 characters* | |
| Beneficiary City | ✓ | ✓ | 1-255 characters* | |
| Beneficiary Country | ✓ | ✓ | 1-255 characters* | |
| Account Number | ✓ | ✓ | 6-34 alphanumeric characters | We validate that the account number provided is a valid one. We do not currently perform checks against the account name. |
| BIC SWIFT | ✓ | ✓ | Valid ISO 9362 SWIFT BIC code; 8 or 11 alphanumeric characters | |
| Payment Currency | ✓ | ✓ | 3 letter ISO currency code | |
| Payment Amount | ✓ | ✓ | Numeric amount | |
| Payment Reference | ✓ | ✓ | 1-255 alphanumeric characters | The scheme only supports 200 alphanumeric characters. The reference field will be truncated to fit this limit. |
| Payment Reason | ✓ | ✓ | 1-255 alphanumeric characters | |
| Payer Entity Type | ✓ | ✓ | ‘individual’ or ‘company’ only | |
| Payer First Name | ✓ | ✕ | 1-255 characters* | |
| Payer Last Name | ✓ | ✕ | 1-255 characters* | |
| Payer Company Name | ✕ | ✓ | 1-255 characters* | |
| Payer Address | ✓ | ✓ | 1-255 characters* | |
| Payer City | ✓ | ✓ | 1-255 characters* | |
| Payer Country | ✓ | ✓ | 2 letter ISO country code | |
| Payer Date of Birth | ✓ | ✕ | ISO 8601 format (YYYY-MM-DD). | |
| Payer Identification Type | ✓ | ✓ | ‘incorporation_number’, ‘passport’ or ‘drivers_license’ only | ‘passport’ or ‘drivers_license’ only for payer entity types of ‘individual’. ‘incorporation_number’ only for payer entity types of ‘company’. |
| Payer Identification Value | ✓ | ✓ | 1-255 characters* |
* Please note that non ASCII characters will be transformed to ASCII equivalent or removed on a best endeavours basis in order to comply with the restrictions of the domestic payment scheme.
SWIFT (Priority) Payment
| Field | Individual | Company | Permitted Data | Notes |
|---|---|---|---|---|
| Beneficiary Entity Type | ✓ | ✓ | ‘individual’ or ‘company’ only | |
| Beneficiary First Name | ✓ | ✕ | 1-255 characters* | |
| Beneficiary Last Name | ✓ | ✕ | 1-255 characters* | |
| Beneficiary Company Name | ✕ | ✓ | 1-255 characters* | |
| Beneficiary Address | ✓ | ✓ | 1-255 characters* | |
| Beneficiary City | ✓ | ✓ | 1-255 characters* | |
| Beneficiary Postcode | ✓ | ✓ | 1-12 characters* | Only required when sending payments to Canada, Mexico and the USA. |
| Beneficiary State or Province | ✓ | ✓ | 1-255 characters* | Only required when sending payments to Canada, Mexico and the USA. |
| Beneficiary Country | ✓ | ✓ | 2 letter ISO country code | |
| IBAN | ✓ | ✓ | 15-34 alphanumeric characters; spaces permitted | IBAN must be used when sending to all IBAN countries. When sending to non-IBAN countries, account number must be used. |
| Account Number | ✓ | ✓ | Varies per destination country | When sending payments to non-IBAN countries, account number must be used. IBAN must be used when sending to all IBAN countries. |
| CLABE | ✓ | ✓ | 18 digits | CLABE must be used instead of account number or IBAN when sending payments in any currency to Mexico. CLABE is the banking standard for the numbering of bank accounts in Mexico (equivalent to the Account Number in other jurisdictions). |
| BIC SWIFT | ✓ | ✓ | Valid ISO 9362 SWIFT BIC code; 8 or 11 alphanumeric characters | BIC SWIFT must be used when sending payments to any country except the USA. When sending to the USA, ABA must be used. |
| ABA | ✓ | ✓ | 9 digits | American banks are identified by a 9 digit ABA number, also known as ‘Routing Number’. The ABA should be valid for FedWIRE payments. Some ABA values are only valid for FedACH payments. Payments to FedACH-only ABAs will fail. The ABA is required for all payments to the USA. |
| Payment Currency | ✓ | ✓ | 3 letter ISO currency code | |
| Payment Amount | ✓ | ✓ | Numeric amount | |
| Payment Reference | ✓ | ✓ | 1-255 alphanumeric characters | The scheme only supports 140 alphanumeric characters. The reference field will be truncated to fit this limit. |
| Payment Reason | ✓ | ✓ | 1-255 alphanumeric characters | The scheme only supports 140 alphanumeric characters. The reference field will be truncated to fit this limit. |
| Payer Entity Type | ✓ | ✓ | ‘individual’ or ‘company’ only | |
| Payer First Name | ✓ | ✕ | 1-255 characters* | |
| Payer Last Name | ✓ | ✕ | 1-255 characters* | |
| Payer Company Name | ✕ | ✓ | 1-255 characters* | |
| Payer Address | ✓ | ✓ | 1-255 characters* | |
| Payer City | ✓ | ✓ | 1-255 characters* | |
| Payer Postcode | ✓ | ✓ | 1-12 characters* | Only required when sending payments to Canada, Mexico and the USA. |
| Payer State or Province | ✓ | ✓ | 1-255 characters* | Only required when sending payments to Canada, Mexico and the USA. |
| Payer Country | ✓ | ✓ | 2 letter ISO country code | |
| Payer Date of Birth | ✓ | ✕ | ISO 8601 format (YYYY-MM-DD). | |
| Payer Identification Type | ✕ | ✓ | ‘incorporation_number’ only | |
| Payer Identification Value | ✕ | ✓ | 1-255 characters* |
* Please note that non-supported characters will be transformed to EBCDIC equivalent or removed on a best endeavors basis in order to comply with the restrictions of the SWIFT payment network. The permitted characters on the SWIFT network are letters, numbers, spaces and the following symbols:
/ – ? : ( ) . , ‘ +
/ – ? : ( ) . , ‘ +
Please be aware that clients sending payments on behalf of their customers need to share their BIC code with us. Further details can be found in our SWIFT BIC – Mandatory Registration and Usage FAQ.