Create a Charge
Create a new charge. An idempotency key is required in the request header to ensure safe retries without creating duplicate charges. This endpoint initializes a payment attempt for the specified amount and channel, returning a charge object that represents the transaction status and payment instructions (e.g., QR string or redirect URL).
Documentation Index
Fetch the complete documentation index at: https://docs.monxa.co/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Body
The amount to be charged, expressed in minor units (e.g., 10000 = 100.00).
The three-letter ISO 4217 currency code (e.g., IDR, MYR, SGD).
The payment channel to be used, such as qr_qris, bank_redirect_fpx, wallet_dana, etc.
qr_qris The type of payment flow, e.g.redirect, or show. Determines how Merchant presents the payment experience to the user.
payload, redirection, embedded Merchant’s unique reference ID for this charge (e.g., order number or invoice ID). Used for reconciliation and idempotency tracking.
Optional short text describing the purpose of the payment or charge. Useful for invoices or customer-facing receipts.
Optional custom key–value pairs for additional information
Response
OK
Unique identifier of the charge
nique charge code generated by Monxa for tracking or reconciliation. (e.g. chg_2510BBFC2A3A6CE22F1B).
Merchant-provided identifier such as invoice or order number.
Unique ID of the merchant who created the charge.
Charge amount in minor units (e.g., 3500 = IDR 35.00).
ISO 4217 currency code (e.g., IDR, MYR, SGD).
The selected payment channel (e.g., qr_qris, bank_redirect_fpx, wallet_dana).
Defines how the charge is presented — e.g., payload, redirection, or embedded.
Current charge status (PENDING, SUCCEEDED, FAILED, etc.).
Merchant’s description of the charge or transaction.
Custom key–value pairs provided in the request for additional context.
Contains payment instructions or URLs to be presented to the customer.
Identifier of the user or API key that created the charge.
Timestamp when the charge was created.
Identifier of the user or process that last updated the charge.
Timestamp of the last update to this charge.