Verified against: Public OpenAPI 2.0.0 · EMI discovery withheld 2026-08-23

Installments

Build an EMI payment flow

The reviewed checkout request can ask Moneybag to show EMI options or preselect an approved EMI configuration. Eligibility and charge calculation remain Moneybag-owned decisions; do not maintain a local eligibility or fee table.

Integration sequence

  1. Create checkout from your trusted backend with the reviewed payment_info fields.
  2. Redirect to the exact hosted checkout URL returned by Moneybag.
  3. Treat the hosted checkout redirect as navigation only.
  4. Verify the resulting transaction before fulfillment.
POST/api/v2/payments/checkout

EMI is represented inside the reviewed checkout request, not by a separate public discovery operation.

{
  "payment_info": {
    "requires_emi": true,
    "emi_configuration_id": "APPROVED_CONFIGURATION_ID",
    "emi_payment_id": "PUBLIC_PAYMENT_SERVICE_UUID"
  }
}

emi_configuration_id is one selected string. emi_payment_id accepts the public payment-service UUID and is the reviewed checkout field; do not substitute the old guide's payment_service_id field.

Never calculate installment fees, settlement amounts, or eligibility locally. Persist only the identifiers and authoritative checkout/verification data your order needs. Do not store card credentials or sensitive authentication data.