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
string
required
Example:
Authorization | Bearer Paste-Your-API-Key-HereRequest Body
string<uuid>
required
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-d2a12797b356integer
required
Nominal amount of payment.
string
Customer email used to send proof of payment or payment reminders.
string
Customer telephone number.
string
General description of the transaction or order.
string
Additional notes for the payment request.
string (format ISO 8601 date-time)
The transaction expiration date and time. After this time, the payment link is
no longer valid.
string
Restrict the payment request to a specific payment method.
string
Cashtag associated with the payment request.
object
Additional custom data attached to the payment request.
Response
Successful ResponseMain Structure (Root)
integer
Status code form API.
string
Status message that describes the status code.
object
The updated payment request data.
data Structure (Object)
string<uuid>
Unique request payment ID.
string
The URL that customers can access to open the payment request.
Errors
object
Returned when the API key is missing or invalid:
{ "statusCode": 401, "messages": "Unauthorized" }.object
Returned when no payment request matches the provided
id:
{ "statusCode": 404, "messages": "Payment not found" }.object
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." }.