📓

Request specifics

• Endpoint: POST /processing/api/v1/intents
• Purpose: Creates an Intent and a Payment for the QRIS payment method.
• Structure: A unified request structure is used for all supported payment methods, but some fields are method-specific.
• For this method:
  • paymentMethodName must be set to QRIS
  • authCurrencyCode must be set to IDR

Intent Request: Example

{
  "clientReferenceId": "1234",
  "payments": [
    {
      "paymentInstrument": {
        "paymentMethodName": "QRIS",
        "incomingDetails": {
          "sessionTimeoutMin": 20
        }
      },
      "submittedAmount": {
        "value": 150000,
        "currency": "IDR"
      },
      "authCurrencyCode": "IDR",
      "webhookUrl": "https://merchant.example.com/webhooks/payments"
    }
  ]
}

Intent Request: Fields Description

📓

Response specifics

• The Intent creation response is generally consistent across all supported payment methods.
• Common fields describe the Intent, the Payment, and the current transaction status.
• Method-specific data is returned in payments[].additionalData.details. Both fields represent the same QR — use one of the two:
  • qrBase64 — the QR as a Base64-encoded PNG image. Display it to the payer as-is.
  • url — the raw EMVCo payload the QR encodes. Use it only if you render the QR image yourself.

Intent Response: Example

{
  "intentId": "232510340021612544",
  "payments": [
    {
      "id": "232510340646563840",
      "submittedAmount": {
        "value": 150000,
        "currency": "IDR"
      },
      "authAmount": {
        "value": 150000,
        "currency": "IDR"
      },
      "paymentInstrument": {
        "id": "PI204264628196626432",
        "paymentMethodId": "PM199507277233246209",
        "paymentMethodName": "QRIS",
        "storedDetails": {
          "sessionTimeoutMin": 20
        }
      },
      "status": "AUTHORIZATION_REQUESTED",
      "additionalData": {
        "details": {
          "qrBase64": "iVBORw0KGgoAAAANSUhEUgAA... (Base64-encoded QR image)",
          "url": "00020101021226610014COM.GO-JEK.WWW01189360091430096736560210G0967365650303UMI51440014ID.CO.QRIS.WWW0215ID10200160245310303UMI5204581253033605802ID5908Merchant6013Jakarta Pusat61051034062070703A016304D11E"
        }
      }
    }
  ],
  "disbursements": [],
  "clientReferenceIntentId": "1234",
  "paymentCreationErrors": [],
  "disbursementCreationErrors": [],
  "intentStatus": "IN_PROGRESS"
}

Response Description

📓

Request specifics

• Endpoint: POST /processing/api/v1/refunds
• Purpose: Creates a Refund for an existing Payment within an Intent.
• For this method: partial must be false or omitted; paymentSubmittedAmount and paymentAuthAmount are not used — the refund always covers the full amount of the original payment.

Refund Request: Example

    {
      "paymentId": 344115072812343296,
      "reason": "Customer requested a refund",
      "clientReferenceId": "070826-1-refund",
      "webhookUrl": "https://merchant.example.com/webhooks/refunds"
    }

Refund Request: Fields Description

📓

Response specifics

• The synchronous response confirms that the refund request has been accepted for processing, not that the money has been returned.
• status is ACCEPTED at this point. The final status arrives via webhook.

Refund Response: Example

    {
      "id": "344115098234117632",
      "intentId": "344115072451633152",
      "paymentId": "344115072812343296",
      "refundSubmittedAmount": {
        "value": 150000,
        "currency": "IDR"
      },
      "refundAuthAmount": {
        "value": 150000,
        "currency": "IDR"
      },
      "reason": "Customer requested a refund",
      "status": "ACCEPTED",
      "createdAt": "2026-09-02T10:15:12.318Z",
      "clientReferenceTransactionId": "070826-1-refund"
    }

Response Description

Case "Successful payment"

Steps:

1. The client creates an intent via POST /processing/api/v1/intents.
2. A synchronous response is returned with status = AUTHORIZATION_REQUESTED.
3. Render the QR from payments[].additionalData.details.qrBase64.
4. A webhook is received with status = CAPTURED.

Case "QR Expired"

Steps:

1. The client creates an intent via POST /processing/api/v1/intents (use the sessionTimeoutMin parameter to shorten the expiration time).
2. A synchronous response is returned with status = AUTHORIZATION_REQUESTED.
3. Wait for the expiration time.
4. A webhook is received with status = CANCELLED.

Case "Payment Declined"

Steps:

1. The client creates an intent via POST /processing/api/v1/intents using the intent.description parameter with the value "DeclinedPayment".
2. A synchronous response is returned with status = AUTHORIZATION_REQUESTED.
3. Render the QR from payments[].additionalData.details.qrBase64.
4. A webhook is received with status = DECLINED.

Case "Failure"

Steps:

1. The client creates an intent via POST /processing/api/v1/intents using the intent.description parameter with the value "LinkCreationError".
2. A synchronous response is returned with status = ERROR.