SFTP Migration
Your existing SFTP connection and file exchange process will remain unchanged throughout the migration. Files will continue to use the same formats and be delivered to and received from the same folders.
The main change is that your entities and accounts will have new Corpay identifiers, as outlined in the relevant reporting and payments guidance below.
SFTP Reporting
Your CAMT.053 files will continue to be delivered to the same folder, at the same time.
What remains the same
SFTP connection will remain unchanged.
CAMT.053 files will continue to be delivered to the same folder.
Files will continue to be delivered at the same time.
File format will remain unchanged.
What you need to change
What you need to change
Your entities and accounts will have new Corpay identifiers.
We will provide the new identifiers and you will need to update your systems to recognise the new entity and account identifiers included in the CAMT.053 files.
SFTP Payments
What remains the same
SFTP connection will remain unchanged.
PAIN.001 files will be submitted to the same folder.
PAIN.002 response files will be delivered to the same folder.
File formats and processing schedules will remain unchanged.
What you need to change
What you need to change
Your paying account and related entities will have new Corpay identifiers. We will provide these and you will need to update your payment process to use the new identifiers.
Corpay’s beneficiary validation rules differ from Alpha’s. Beneficiary data must therefore meet Corpay’s validation requirements for payments to be accepted.
Beneficiaries
You will need to provide the beneficiary and beneficiary bank details using separate address fields.
The XML tags below identify the relevant fields in your file.
1. Your paying account
Field: DbtrAcct / Id / Othr / Id
Use your new Corpay account ID. You will have a separate account ID for each currency.
Do not use your old RM ID, such as CA-0022927.
Field: DbtrAcct / Ccy
Use the currency of the Corpay account you are paying from, for example GBP, EUR, USD or CAD.
Example:
<DbtrAcct>
<Id>
<Othr>
<Id>610325577000011004</Id>
</Othr>
</Id>
<Ccy>GBP</Ccy>
</DbtrAcct>Your new account IDs will be provided to you. Use the ID that matches the currency of the payment.
2. Beneficiary details
RM often accepted a beneficiary name and IBAN, or a single free-text address. Corpay requires the beneficiary’s name and address to be provided in separate fields under Cdtr.
| XML field | Description | Requirement |
|---|---|---|
Cdtr / Nm | Beneficiary name | Required |
Cdtr / PstlAdr / StrtNm | Street | Required |
Cdtr / PstlAdr / TwnNm | City | Required |
Cdtr / PstlAdr / Ctry | Country, such as GB, DE or US | Required |
Cdtr / PstlAdr / PstCd | Postcode | Required for the US and Canada |
Cdtr / PstlAdr / CtrySubDvsn | State or province | Required for the US and Canada |
Do not place the complete address in AdrLine while leaving the city or country fields empty. The city, using TwnNm, and country, using Ctry, must be provided as separate fields.
3. Beneficiary bank details
RM often only required a BIC. Corpay also requires the beneficiary bank’s name and address under CdtrAgt / FinInstnId.
| XML field | Description | Requirement |
|---|---|---|
Nm | Bank name | Required |
BIC or BICFI | SWIFT/BIC | Always provide where available |
PstlAdr / StrtNm | Bank street | Required |
PstlAdr / TwnNm | Bank city | Required |
PstlAdr / Ctry | Bank country | Required |
PstlAdr / PstCd | Bank postcode | Required for the US and Canada |
PstlAdr / CtrySubDvsn | Bank state or province | Required for the US and Canada |
The bank country must be the country where the beneficiary’s bank is located. It does not necessarily need to be the beneficiary’s country.
4. Beneficiary account details
Provide the beneficiary’s account details under CdtrAcct.
Send either an IBAN or a local account number with the required routing information. Do not send both for the same payment.
Europe and other IBAN countries
For payments to IBAN countries, such as Germany, France and Ireland:
CdtrAcct / Id / IBANUse the beneficiary’s IBAN.
A local account number without an IBAN will fail for these payment corridors.
UK pounds — GB-GBP
Choose one of the following options:
Option 1: GB IBAN
CdtrAcct / Id / IBANOption 2: UK local account details
CdtrAcct / Id / Othr / IdUse the 8-digit account number.
Also provide:
CdtrAgt / FinInstnId / ClrSysMmbId / MmbIdUse the 6-digit sort code.
United States — USD to a US bank
Provide:
CdtrAcct / Id / Othr / IdUse the beneficiary’s account number.
Also provide:
CdtrAgt / FinInstnId / ClrSysMmbId / MmbIdUse the 9-digit ABA routing number.
Canada
Provide:
CdtrAcct / Id / Othr / IdUse the beneficiary’s account number.
Also provide:
CdtrAgt / FinInstnId / ClrSysMmbId / MmbIdUse the 9-digit routing number.
For payments to Canada, provide the postcode and province for both the beneficiary and the beneficiary’s bank.
Australia — AUD
Provide:
CdtrAcct / Id / Othr / IdUse the beneficiary’s account number.
Also provide:
CdtrAgt / FinInstnId / ClrSysMmbId / MmbIdUse the 6-digit BSB.
5. Fields unchanged from RM
The following fields remain unchanged:
| Payment information | XML field |
|---|---|
| Amount and currency | Amt / InstdAmt |
| Payment date | ReqdExctnDt |
| Your reference | RmtInf / Ustrd |
| End-to-end ID | PmtId / EndToEndId |
| Purpose of payment, if already provided | Purp |
Checklist
Before submitting a pain.001 file, confirm that:
-
DbtrAcctcontains your new Corpay account ID, not your oldCA-...RM ID. -
DbtrAcct / Ccymatches the currency of the Corpay account. -
Cdtrcontains the beneficiary name, street, city and country. -
CdtrAgtcontains the bank name, street, city, country and BIC. -
CdtrAcctcontains either an IBAN or a local account number with the required routing, sort code or BSB. - For payments to the US and Canada, the postcode and state or province are provided for both the beneficiary and the beneficiary’s bank.
Updated about 15 hours ago
