Other Journeys in ‘Appendices’.
Standing Order Frequency Examples
Every working day
Every week, on the 3rd day of the week.
Every 2nd week, on the 3rd day of the week.
Every month, on the 2nd week of the month, and on the 3rd day of the week.
Every month, on the last day of the month.
Every 6th month, on the 15th day of the month.
Paid on the 25th March, 24th June, 29th September and 25th December.
Payments initiated by PISPs using Open Banking Write APIs, should be able to cover the following international payments charge models:
In order to make an International Payment, the ASPSP will need some of the following details relating to the Beneficiary’s bank account:
The Account Holders NameThe recipient's full name.
SWIFT/BIC CodeA SWIFT Code consists of 8 or 11 characters, both numbers and letters e.g. RFXLGB2L.
Sort CodeUK Bank code (6 digits usually displayed as 3 pairs of numbers), optional if within EEA.
Routing NumberThe American Bankers Association Number (consists of 9 digits) and is also called a ABA Routing Number.
Routing CodeAny other local Bank Code - e.g. BSB number in Australia and New Zealand (6 digits).
IFSC CodeIndian Financial System Code, which is a unique 11-digit code that identifies the bank branch i.e. ICIC0001245.
IBANThe International Bank Account Number.
Bank NameThe name of the bank where the recipient's account is held.
Bank AddressThe address of the Beneficiary's bank.
Account NumberThe recipient's bank account number.
The information required is different for each country. For further information please see the table below:
Note: Whilst the SWIFT BIC is required to route the payments, for payments in Euro the customer does not have to provide this, the sending bank must derive it from the beneficiary IBAN
Deep Linking for App-to-App redirection Previous
Card-specific Permissions and Data Clusters for AIS journeys Next