The payment request to update is selected by the
id field in the request
body, not by the {uuId} segment in the URL path. The path segment is
cosmetic and is ignored by the API — always send the target payment request
id in the body.Authorization
Example:
Authorization | Bearer Paste-Your-API-Key-HereRequest Body
A unique identifier obtained when creating a single payment request. This selects
the payment request to update (the
{uuId} URL segment is ignored).Example:6f8c19ff-5b97-4792-aa89-d2a12797b356Nominal amount of payment.
Customer email used to send proof of payment or payment reminders.
Customer telephone number.
General description of the transaction or order.
Additional notes for the payment request.
The transaction expiration date and time. After this time, the payment link is
no longer valid.
Restrict the payment request to a specific payment method.
Cashtag associated with the payment request.
Additional custom data attached to the payment request.
Response
Successful ResponseMain Structure (Root)
Status code form API.
Status message that describes the status code.
The updated payment request data.
data Structure (Object)
Unique request payment ID.
The URL that customers can access to open the payment request.
Errors
Returned when the API key is missing or invalid:
{ "statusCode": 401, "messages": "Unauthorized" }.Returned when no payment request matches the provided
id:
{ "statusCode": 404, "messages": "Payment not found" }.Returned when the payment request has already been paid and can no longer be
edited:
{ "statusCode": 409, "messages": "Transaction already paid. Cannot edit payment request." }.