Create a payment

post

https://api.crossborder.jiopay.co.in/api/v1/payment

Creates a payment for an order or subscription. For initial payments, card details and a callback URL are required. For subsequent payments on as_presented subscriptions, the card from the last successful payment is reused, and request_id, amount, and currency are required instead.

Either order_id or subscription_id must be provided, but not both.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Either order_id or subscription_id must be provided, but not both. For initial payments, card and callback_url are required. For subsequent payments on as_presented subscriptions, the card from the last successful payment is reused, and request_id, amount, and currency are required instead.

order_id

string

The unique identifier for the order. Either order_id or subscription_id must be provided, but not both.

subscription_id

string

The unique identifier for the subscription. Either order_id or subscription_id must be provided, but not both.

method

string

enum

Payment method. Must be card. Required for initial payments. Not required for subsequent payments (defaults to card).

Allowed:

sequence

string

enum

Payment sequence. Use initial (default) for first-time payments or subsequent for merchant-initiated payments on as_presented subscriptions.

Allowed:

card

object

Card details. Required for initial payments. Not required for subsequent payments — the card from the last successful payment is reused.

callback_url

string

HTTPS URL where the customer is redirected after payment processing. Required for initial payments. Not required for subsequent payments as there is no customer redirect involved.

request_id

string

Idempotency key. Required for subsequent payments, optional for initial payments.

amount

integer

Payment amount in minor units (cents). Required for subsequent subscription payments. Cannot exceed the subscription's max_amount.

currency

string

Currency code in ISO 4217 format. Must match the subscription's currency for subsequent payments.

notes

object | null

Optional key-value pairs for attaching custom metadata (e.g. invoice references, project codes). Keys must be strings and cannot collide with reserved field names. If your business has custom field rules configured (e.g. enum constraints), values are validated against those rules. Each key appears as a separate column in CSV report exports, with corresponding values populating the rows.

Responses

201Created

400Bad Request