This table lists the most likely balance type values to be returned in the response from the GET Balance call. We map the balance type code used by the bank to the corresponding ISO 20022 standard code if they provide it.
These codes are mostly used for accounting purposes. You can find a full list of codes here.
|AVLB||Available||Balance of money that is at the disposal of the account owner at the date specified|
|BOOK||Book||Balance that is registered in the books of the account holder’s IBAN|
|CLSG||Closing||Booked balance at the end of the bank’s business day (sum of credits and debit booked transactions)|
|CRRT||Current||Balance of an account at a precise moment in time|
|EXPN||Expenses Balance||Balance attributed to expenses.|
|OTHR||Other||Balance that is not explicitly defined|
|PDNG||Pending||Balance that is pending the settlement of a transaction|
This table lists the most likely account types to be returned from the GET accounts endpoint. The types are based on the ISO 20022 standard, and you can find a full list of codes here.
|CACC||Current||Account used to post credits and debits when no specific account has been specified|
|CASH||Cash Payments||Account used for the payment of cash|
|SLRY||Salary||Account used for salary payments|
|SVGS||Savings||Account used for savings|
This table lists the most likely payment status values to be returned after payment initiation. Payment status indicates the payment's current life cycle stage. A standard successful payment life cycle is as follows:
The types are based on the ISO 20022 standard, and you can find a full list of codes here.
|RCVD||Received||The payment has been received and is awaiting Strong Customer Authentication|
|ACCP||AcceptedCustomerProfile||The preceding check of technical validation was successful. The customer profile check was also successful.|
|ACSP||Accepted Settlement In Progress||The payment has been sent by the bank but is not yet settled in the creditor account.|
|ACSC||Accepted Settlement Completed||The payment has been sent by the bank and settled in the creditor's account.|
|NAUT||NotAuthorized||The end-user has cancelled the payment authorization.|
|RJCT||Rejected||The payment has failed due to insufficient funds in the debtor's account|
|PDNG||Pending||The debtor account holder has edited the payment in their online banking and a new Strong Customer Authentication is now pending|
|CANC||Cancelled||The payment has been deleted by the end-user|
|PRSY||OnHold||The payment initiation was put on hold by the bank|
|PATC||Partially Accepted||The payment requires a second authorization|
This table lists the five ISO 20022 values that are accepted as
paymentContextCode parameters in the
paymentMetadata object for Payments. This parameter is used to classify payments.
It is not mandatory to send the parameter, but several banks across Europe request it to be added to help with their anti-fraud monitoring. When the purpose of a payment is given, the bank will use that information to help determine if the payment can be exempted from payment authorization.
|GDDS||Commercial||Use this code if your payment is a commercial person-to-business (P2B) where the consumer is buying goods.|
|IVPT||Bill or Invoice||Use this code if your payment is a bill or invoice payment.|
|MP2P||Party to Party||Use this code if your payment is a non-commercial party-to-party (P2P) payment.|
|OTHR||Other||Use this if your payment doesn't fit any of the other categories of payments.|
|SCVE||Online or Electronic payments||Use this code if your payment is a commercial person-to-business (P2B) where the consumer is buying services.|
Updated 25 days ago