Get account by id.
OAuth Grant type use on OpenAPI subscriptions, Private JWT
Client ID header
Customer unique id.
Account unique identifier generated by PagoNxt.
Format used for the account number in the accountId property.
The possible values are:
- IBAN = IBAN code
- BBAN = Basic Bank Account Number (BBAN) that represents a country-specific bank account number. Each country has its own standards for the format and length of the BBAN. The value is at most 31 char or 35 bytes long.
- UUID = Unique account identifier. It is an internal code to uniquely identify the account. Some accounts are internal so they have UUID but no IBAN/BBAN.
For example:
- In UK, the BBAN format is: Bank(4) + Sort code(6) + Account(8)
- In Spain, it is: Banco(4) + Sucursal(4) + CD(2) + CTA(10)
Country code. The value is based on the ISO 3166-1 alpha-2 (https://www.iso.org/obp/ui/#search/code/). Required with account_id_type BBAN.
Account response.
{
"accountIdentifiers": [
{
"accountIdType": "uuid",
"accountId": "0589bd6c-cca4-4b46-9c8a-b786171e66e1",
"country": "GB"
},
{
"accountIdType": "iban",
"accountId": "GB40PNXT09991100000010",
"country": "GB"
},
{
"accountIdType": "bban",
"accountId": "PNXT09991100000010",
"country": "GB"
}
],
"customerId": "PNXTGB2LXXXUS1234567890",
"baseCurrency": "EUR",
"productName": "eMoney Account",
"nickName": "My E Money Account",
"reconciliationModel": "PS-REF",
"supplementaryId": "PN2345ABCD",
"virtualAccountStructureId": "42dbdc87-a491-4566-bb97-eb2d9aea4707",
"legalEntity": {
"bic": "PNXTGB2LXXX",
"legalEntityId": "pagonxt_uk",
"legalEntityName": "PagoNxt OneTrade UK Ltd"
},
"balances": {
"available": {
"amount": {
"amount": 99.99,
"currency": "GBP"
},
"lastChangeDateTime": "2017-07-21T17:32:28Z"
}
},
"createdAt": "2024-11-08T16:08:36.068Z",
"updatedAt": "2024-11-06T16:08:36.068Z",
"_links": {
"self": {
"href": "https://{host}/accounts/0589bd6c-cca4-4b46-9c8a-b786171e66e1"
}
}
}Date and time when the entry was created.
Date and time when the entry was updated.
Customer unique id.
Currency code. The value is the alpha-3 format defined in ISO 4217 (https://www.iso.org/iso-4217-currency-codes.html).
Unique identifier for an account's virtual account structure. Present for all virtual accounts and real accounts with related virtual accounts.
Account reconciliation model. Determines how an account's collections will be reconciled. Only present in real acount. Option are:
PS-VA: Payment subject virtual account
PS-REF: Payment subject referencePS-VA
COL-VA: Collection virtual account
COL-REF: Collection reference
List of account identifiers.
Account identifier. Type depends on accountIdType.
Format used for the account number in the accountId property.
The possible values are:
- IBAN = IBAN code
- BBAN = Basic Bank Account Number (BBAN) that represents a country-specific bank account number. Each country has its own standards for the format and length of the BBAN. The value is at most 31 char or 35 bytes long.
- UUID = Unique account identifier. It is an internal code to uniquely identify the account. Some accounts are internal so they have UUID but no IBAN/BBAN.
For example:
- In UK, the BBAN format is: Bank(4) + Sort code(6) + Account(8)
- In Spain, it is: Banco(4) + Sucursal(4) + CD(2) + CTA(10)
Country code. The value is based on the ISO 3166-1 alpha-2 (https://www.iso.org/obp/ui/#search/code/).
NickName account Name (alias) that the customer has assigned to the account for easy identification.
Name of the product associated with the account
Account reference for referenced virtual accounts. Unique by customer and real account.
Legal Entity details object.
Bic of the legal entity associated with the account.
Unique identifier of the legal entity associated with the account.
Legal Name of the legal entity associated with the account.
List of real account identifiers.
Account identifier. Type depends on accountIdType.
Format used for the account number in the accountId property.
The possible values are:
- IBAN = IBAN code
- BBAN = Basic Bank Account Number (BBAN) that represents a country-specific bank account number. Each country has its own standards for the format and length of the BBAN. The value is at most 31 char or 35 bytes long.
- UUID = Unique account identifier. It is an internal code to uniquely identify the account. Some accounts are internal so they have UUID but no IBAN/BBAN.
For example:
- In UK, the BBAN format is: Bank(4) + Sort code(6) + Account(8)
- In Spain, it is: Banco(4) + Sucursal(4) + CD(2) + CTA(10)
Country code. The value is based on the ISO 3166-1 alpha-2 (https://www.iso.org/obp/ui/#search/code/).
Account balances object.
Available balance object.
The value uses the data format defined in ISO 20022 and has a maximum of 18 digits, of which 5 can be decimals, separated by a point.
Data in ISO 20022 format containing up to 18 digits from which 5 may be decimals.
Separation is a point.
Currency code. The value is the alpha-3 format defined in ISO 4217 (https://www.iso.org/iso-4217-currency-codes.html).
Last update date time.
The date format is 'yyyy-MM-ddThh:mm:ss.fff±timezone', where fff are milliseconds and timezone can be 'Z' or 'hh:mm'', type: BalanceAmount
Single links object.
Self links object.
Self link.
Bad Request
{
"errors": [
{
"code": "BAD_REQUEST",
"message": "Bad Request",
"level": "FATAL",
"description": "Description of the Bad Request error"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Unauthorized
{
"errors": [
{
"code": "UNAUTHORIZED",
"message": "Unauthorized",
"level": "FATAL",
"description": "Description of the Unauthorized error"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Forbidden
{
"errors": [
{
"code": "FORBIDDEN",
"message": "Forbidden",
"level": "FATAL",
"description": "Description of the Forbidden error"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Not Found
{
"errors": [
{
"code": "NOT_FOUND",
"message": "Not Found",
"level": "FATAL",
"description": "Description of the Not Found error"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Not Acceptable The Accept header does not specifically contain one of the allowable types. Missing Accept header, usually 'application/json'
{
"errors": [
{
"code": "NOT_ACCEPTABLE",
"message": "Not Acceptable",
"level": "FATAL",
"description": "Description of the Not Acceptable error"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Request Entity Too Large Most web servers have a limit of 8192 bytes (8 KB). The server will close the connection to prevent the client from continuing the request.
{
"errors": [
{
"code": "ENTITY_TOO_LARGE",
"message": "Request Entity Too Large",
"level": "FATAL",
"description": "Description of the Request Entity Too Large error"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
URI Too Long
{
"errors": [
{
"code": "URI_TOO_LONG",
"level": "FATAL",
"message": "URI Too Long",
"description": "URI Too Long description"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Unprocessable Entity
{
"errors": [
{
"code": "UNPROCESSABLE_ENTITY",
"level": "FATAL",
"message": "Unprocessable Entity",
"description": "Unprocessable Entity description"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Too Many Requests
{
"errors": [
{
"code": "TOO_MANY_REQUESTS",
"level": "ERROR",
"message": "Too Many Requests",
"description": "Too Many Requests description"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Internal server error
{
"errors": [
{
"code": "INTERNAL_SERVER_ERROR",
"level": "FATAL",
"message": "Internal server error",
"description": "Internal server error description"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Service unavailable
{
"errors": [
{
"code": "SERVICE_UNAVAILABLE",
"level": "ERROR",
"message": "Service unavailable",
"description": "Service unavailable error description"
}
]
}{
"errors": [
{
"code": "fail",
"level": "ERROR",
"message": "Health check failed",
"description": "Health check failed"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Gateway timeout
{
"errors": [
{
"code": "GATEWAY_TIMEOUT",
"level": "ERROR",
"message": "Gateway timeout",
"description": "Gateway timeout error description"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue
Default error
{
"errors": [
{
"code": "INTERNAL_SERVER_ERROR",
"level": "FATAL",
"message": "Error message",
"description": "Error description"
}
]
}Data structure containing the details for errors
Array of errors
Data structure containing the error details
Unique alphanumeric human readable error code
Brief summary of the reported issue
Level of the reported issue. The possible values are.
- ERROR
- FATAL
- INFO
- WARNING
Detailed description of the reported issue