Payments
Initiate and complete payments against an order. These endpoints handle the core payment processing flow, including method selection, authentication, and payment confirmation.
POST
Initiate a Payment [v3]Initiate a payment for an order after the customer has selected their payment mode and provided the required details. The response guides the subsequent payment flow — redirect for cards/netbanking, OTP for pay later, or QR for UPI.
POSTComplete a Payment [v3]Complete a payment that has already been initiated by submitting an OTP or authorization token. Currently used for certain Pay Later providers where you want to offer a native OTP input experience on your checkout page. The `payment_flow` value comes from the Initiate Payment response's `next` actions array.
POSTResend an OTP [v3]Request a new OTP for a payment that requires OTP-based completion. Wait at least 30 seconds before requesting a resend. There is a limit of 2 additional OTP requests per transaction — exceeding this limit marks the transaction as failed.
POSTCapture a Payment [v3]Capture a pre-authorized payment transaction. Only applicable when the sub-merchant account has `capture_mode=manual` configured. Nimbbl exposes a single interface across every supported payment partner — you don't need partner-specific logic.
POSTVoid a Payment [v3]Void (cancel) a pre-authorized payment transaction, releasing the held funds back to the customer. Only applicable when the sub-merchant account has `capture_mode=manual` configured. Nimbbl exposes a single interface across every supported payment partner — you don't need partner-specific logic.