Unique identifier as defined by BillDesk for each merchant

Transaction amount in two decimals, eg. 299.28

Unique ID generated by the merchant for each request

ISO currency code of the transaction amount, for INR this value will be 356

BillDesk defined unique identifier for acquirer Mandatory for Upi and Netbanking flows

Itemcode value as provided by BillDesk, with a default value DIRECT

Represents the type of authentication initiated in the request, will be fixed value - 3ds2

Value that determines which entity will capture the device attributes, possible values are merchant

Merchants URL where the customer will be redirected after a transaction is completed

Represents the method of payment, and can take the following values - card, netbanking, wallet, upi, eft, bankaccount, cashcard, cardless (non-card emi option) The associated object will also be provided in the request.

Indicates transaction processing type, will be the following values: AFA payment • card - 3ds or y3ds or 3ds_redirect • upi – collect, qr or intent • netbanking – nb • eft - offline Recurring payment • card, upi, bankaccount – si

BD-TraceID is a unique identifier passed by the merchant to ensure request idempotency. Requests with identical BD-TraceID within a 24 hour window would fail.

Request timestamp to identify date and time of origin of request. Example, a value of BD-Timestamp 20210113180403 identifies the request to have originated on 13th January 2021 at 06:04:03 PM.

Accept Response Content-Type to take the values application/jose

Request Content-Type to take the values application/jose