Updates a multi invoice payment link.
OAuth Grant type use on OpenAPI subscriptions, Private JWT
Client ID header.
Customer unique uuid.
Multi invoice payment link unique id.
Update payment link by id.
Update multi invoice payment link.
Update multi invoice payment link example.
{
"status": "CANCELLED"
}This allows to cancell a multi invoice payment link.
Multi invoice payment link response.
{
"id": "41ac864b-7698-4cb5-880f-e383204ae67d",
"currencyCode": "EUR",
"realAccountId": "8bd407a4-3cfb-4ca9-aeca-0e07c3ccf408",
"customerId": "pagonxt_esESG19966464",
"paymentSubjectId": "df6ebe87-7a29-4812-9d14-e2c5f78d8260",
"description": "DESCRIPTION",
"status": "CANCELLED",
"url": "https://onetrade.dev.api.pagonxt.com/em-cs-payment-form/em-cs-payment-form/pagonxt/init-multi-invoice-payment?v=0f6466db82b33f00b6ea9b53983b08acd43a2bd224d15c8a96b166a957376391&mid=B_OenbyfJZjR1h&cid=pagonxt_esESG19966464",
"expirationDate": "2026-01-26T11:10:54.384Z",
"successCallback": "https://pagonext.com/university/success",
"failureCallback": "https://pagonext.com/university/failure",
"externalPaymentReference": "REF",
"paymentMethods": [
"BANK_TRANSFER"
],
"totalAmount": 33,
"selectedAmount": 0,
"totalInvoiceCount": 22,
"selectedInvoiceCount": 0,
"paymentSubjectExternalId": "extId",
"createdAt": "2026-01-23T11:10:54.372Z",
"updatedAt": "2026-01-23T11:10:54.372Z",
"_links": {
"self": {
"href": "https://onetrade.dev.api.pagonxt.com/?_offset=0&_limit=10"
}
}
}Date and time when the entry was created.
Date and time when the entry was updated.
A Universally Unique Identifier (UUID) is a 128-bit label used to uniquely identify information in computer systems without a central registration authority. Standardized by RFC 9562 (formerly RFC 4122), UUIDs are usually represented as 32 hexadecimal digits separated by hyphens into five groups (e.g., 550e8400-e29b-41d4-a716-446655440000). They ensure extremely low collision probability, making them ideal for distributed systems.
Customer unique uuid.
Total added amount of all the invoices of this multi invoice payment link.
Total selected to pay amount of this multi invoice payment link.
Total number of invoices of this multi invoice payment link.
Number of selected to pay invoices of this multi invoice payment link.
Currency code. The value is the alpha-3 format defined in ISO 4217 (https://www.iso.org/iso-4217-currency-codes.html).
Payment subject associated to this multi invoice payment link.
Payment subject external id associated to this multi invoice payment link.
Real account associated to this multi invoice payment link.
Payment link status.
The possible values are:
- GENERATED = Payment link has been created but has not yet been used to make a payment.
- COMPLETED = Payment link has been payed.
- CANCELLED = Payment link has been cancelled and cannot been used to make a payment.
- IN_PROGRESS = Payment link is in a payment process.
- UPDATING_INVOICES = Payment link is creating async invoices.
It is a URL for redirection in case the payment is positive, to an address set by the customer itself.
It is a URL for redirection in case the payment is negative, to an address set by the customer itself.
Payment reference used by PagoNxt for reconciliation purposes.
External payment reference provided by customer.
Payment link purpose.
Date and time when the multi invoice payment link expires.
The value uses the data format defined in ISO 8601 and is expressed in UTC time:
'YYYY-MM-DDThh:mm:ss.sssZ'.
Multi invoice payment link URL to be sent to the payment subject.
Payment methods available for the payment link.
Single links response object.
Self links response object.
Self response link href.
Indicates that the server would not process the request due to something the server considered to be a client error.
{
"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 response 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.
Indicates that a request was not successful because it lacks valid authentication credentials for the requested resource.
{
"errors": [
{
"code": "UNAUTHORIZED",
"message": "Unauthorized",
"level": "FATAL",
"description": "Description of the Unauthorized error"
}
]
}Data structure containing the details for errors
Array of response 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.
Indicates that the server understood the request but refused to process it.
{
"errors": [
{
"code": "FORBIDDEN",
"message": "Forbidden",
"level": "FATAL",
"description": "Description of the Forbidden error"
}
]
}Data structure containing the details for errors
Array of response 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.
Indicates that the server cannot find the requested resource.
{
"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 response 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 response 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 response 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.
Indicates that a URI requested by the client was longer than the server is willing to interpret.
{
"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 response 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 response 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.
Indicates that the server understood the content type of the request content, and the syntax of the request content was correct, but it was unable to process the contained instructions.
{
"errors": [
{
"code": "UNPROCESSABLE_ENTITY",
"level": "FATAL",
"message": "Unprocessable Entity",
"description": "Unprocessable Entity description"
}
]
}Data structure containing the details for errors
Array of response 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.
Indicates the client has sent too many requests in a given amount of time.
{
"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 response 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.
Indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
{
"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 response 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.
Indicates that the server is not ready to handle the request.
{
"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 response 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.
Indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server in order to complete the request.
{
"errors": [
{
"code": "GATEWAY_TIMEOUT",
"level": "ERROR",
"message": "Gateway timeout",
"description": "Gateway timeout error description"
}
]
}Data structure containing the details for errors
Array of response 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.
Error used by efault.
{
"errors": [
{
"code": "INTERNAL_SERVER_ERROR",
"level": "FATAL",
"message": "Error message",
"description": "Error description"
}
]
}Data structure containing the details for errors
Array of response 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.