The setting to charge admin fee and channel fee to the customer does not
apply to the Request Payment feature.
Authorization
Request Body
URL where the buyer is redirected after a successful payment. Supported only
when the created record can persist it. If the platform cannot store the value,
the request is rejected loudly with
{ "statusCode": 400, "messages": "redirectUrl is not supported on payment requests and was not saved" }
rather than silently dropping it. When persisted, the value is echoed in the
response as data.redirectUrl.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 (lowercase). Accepts
one of the following values:
qrisva/bniva/briva/mandiriva/cimbva/permatava/bjbva/bsiewallet/danaewallet/gopayewallet/linkajaewallet/shopeepayewallet/jeniusoutlet/alfamart
400 with
"Payment method \"...\" is not available or disabled".paymentMethod determines the payment code returned by the API (for example a
VA number or a QRIS payload) for that specific method. The Mayar checkout page
link (link) still follows the payment methods configured in your Mayar
settings.Cashtag associated with the payment request. Only required when using
ewallet/jeniuspay as the paymentMethod.Response
Successful ResponseMain Structure (Root)
data Structure (Object)
The redirect URL that was persisted with the payment request, or
null when
none was provided.Errors
Returned when the request body fails validation:
{ "statusCode": 400, "messages": "Validation Error" }.Returned when
redirectUrl was provided but the payment-request record cannot
persist it:
{ "statusCode": 400, "messages": "redirectUrl is not supported on payment requests and was not saved" }.Returned when a payment request with the same identifier already exists:
{ "statusCode": 409, "messages": "already exist" }.