Create a new payment subject.
OAuth Grant type use on OpenAPI subscriptions, Private JWT
Client ID header
Customer unique id.
Create payment subject request body.
Create person payment subject.
Create person payment subject example.
{
"externalId": "extid3",
"metadataType": "PERSON",
"supplementaryReference": "PN2222AAAA",
"metadata": {
"name": "Juan",
"lastName": "Gonzales",
"dateOfBirth": "2024-12-01",
"idNumber": "25073259Q",
"email": "hello@myemail.com"
}
}Create company payment subject.
Create company payment subject example.
{
"externalId": "extid3",
"metadataType": "COMPANY",
"supplementaryReference": "PN2222AAAA",
"metadata": {
"name": "My Company S.A.",
"taxId": "25073259Q",
"email": "hello@mycompany.com"
}
}External ID used to identify the payment subject by the customer.
Unique supplementary reference that can be optionally provided by our customer.
Type of the extra info attached to a payment subject. It can be PERSON or COMPANY.
Optional metadata info. Available properties for PERSON: name, lastName, idNumber, email and dateOfBirth. Available properties for COMPANY: name, email and taxId.
Company name.
Person last name.
Company email.
Person birth date.
Optional identification number that can be the national id, passport or any other id of the person. It's a free string.
Tax id of the company.
Parent real account UUID. If provided, a virtual account under this real account will be assigned to the new payment subject.
New payment subject response.
{
"id": "8ff529e3-d6c8-4ee6-afe3-b71c05e06f63",
"customerId": "eventTEST251024",
"externalId": "1000",
"metadataType": "PERSON",
"createdAt": "2024-12-09T11:08:06.721Z",
"updatedAt": "2024-12-09T11:08:06.721Z",
"customer": {
"id": "eventTEST251024",
"name": "Phone Company",
"address": "Calle Nueva, 28001, Madrid, MADRID, ES"
},
"virtualAccount": {
"accountIdentifiers": [
{
"accountIdType": "uuid",
"accountId": "fbb5217f-2a88-47cd-8ad8-5df73afdf9b1"
},
{
"accountIdType": "iban",
"accountId": "ES0967222000420000004643"
},
{
"accountIdType": "bban",
"accountId": "67222000420000004643",
"country": "ES"
}
],
"realAccountId": "76a251e2-59c6-4de9-96a2-911cf13519a0",
"legalEntityBic": "PAGOES22XXX"
},
"metadata": {
"name": "Juan",
"lastName": "Gonzales",
"dateOfBirth": "2024-12-01",
"idNumber": "25073259Q"
},
"_links": {
"self": {
"href": "https://host/customers/eventTEST251024/payment_subjects/8ff529e3-d6c8-4ee6-afe3-b71c05e06f63"
}
}
}Date and time when the entry was created.
Date and time when the entry was updated.
Unique identifier.
Customer unique id.
External ID used to identify the payment subject by the customer.
Unique supplementary reference that can be optionally provided by our customer.
Type of the extra info attached to a payment subject. It can be PERSON or COMPANY.
Optional metadata info. Available properties for PERSON: name, lastName, idNumber, email and dateOfBirth. Available properties for COMPANY: name, email and taxId.
Company name.
Person last name.
Company email.
Person birth date.
Optional identification number that can be the national id, passport or any other id of the person. It's a free string.
Tax id of the company.
New payment subject virtual account. Only created if a real account id is provided.
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/).
Account reference for referenced virtual accounts. Unique by customer and real account.
Bic of the legal entity associated with the account.
Parent real account unique identifier.
New payment subject customer. Only returned when a virtual account is created for the payment subject.
Customer unique id.
Customer company name.
Customer company address.
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
Unsupported Media Type. The requested content type is not supported by the REST service
{
"errors": [
{
"code": "UNSUPPORTED_MEDIA_TYPE",
"message": "Unsupported Media Type",
"level": "FATAL",
"description": "Description of the Unsupported Media Type 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
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