Sale using Visa Card API

This field must contain the PG instance ID.

This field must contain the merchant ID.

This field must contain the any of the following action to be performed: * SERVICE_POST_MPI, * SERVICE_POST_MPI_SI, * SERVICE_POST_MPI_RECURRING

This field includes the ISO Code for the currency of amount field. For INR this is 356. If not passed default currency would be used. Length: 3 characters.

This field must include PG acquiring Bank ID.

This field must include the Visa/Master card number. All the digits as a continuous string without formatting ALT ID to be passed for domestic guest checkout transactions.

This field is Mandatory for Domestic guest checkout transactions.

This is used to pass Stored Card Credential Indicator. * 1 - First transaction of Recurring Payment – Registration (normal PAN and token PAN) * 2 - Subsequent transaction (normal PAN and token PAN) * 3 - When capturing a stored credential for the first time i.e., Storing PAN for the first time * 4 - When initiating a transaction using an already stored credential * 5 - If the token credential is getting stored for first time i.e., Post Successful Authorization, Token will be generated & stored. * 6 - When initiating a Normal ecommerce transaction using an already Token stored credential 0/no value - Normal eCommerce transaction

This field must include Cryptogram value, which is received from Token Vault for only Tokenized transactions. Cryptogram is mandatory for Token transactions and ALT ID transactions. Cryptogram is optional for Subsequent recurring transactions.

This field includes a valid card expiry year in the format yyyy .ALT ID expiry to be passed for domestic guest checkout transactions.

This field includes a valid card expiry month in the format MM. ALT ID expiry to be passed for domestic guest checkout transactions

This field is must contain the name on card.

This field is must contain the valid customer email ID.

This field must include merchant reference number

This field must include brief description of items purchased. Character Limit: 0-50 characters.

This field must include the CVV printed at the back of the card.

This field includes a Transaction ID from MPI. This is mandatory for Pre-auth & Sale and optional for recurring transactions

This field includes a status from MPI. It is mandatory for Pre-auth & Sale and optional for recurring transactions.

This field includes a ECI from MPI. It is mandatory for Pre-auth & Sale and optional for recurring transactions.

This field includes a CAVV or AVV from MPI. It is an encoded value. It is mandatory for Pre-auth & Sale and optional for recurring transactions.

This field includes status from MPI. It is mandatory for Pre-auth & Sale and optional for recurring transactions.

This field includes is a hash of the fields sent to ensure that no modification is done in transit between Merchant/PG and web servers. Composition of message_hash for service post mpi, preauth and si registration SERVICE-POSTMPI:17:Base64( SHA1(pg_instance_id|merchant_id|action| currency_code|amount|merchant_reference_no|p an|exp_date_yyyyexp_date_mm|cvv2|name_on_ card|customer_device_id|mpiId|status|eci|xid|cav v|key|)) Composition of message_hash for service post recurring SERVICE-POSTMPI:17:Base64( SHA1(pg_instance_id|merchant_id|action| currency_code|amount|merchant_reference_no |name_on_card|siUniqueRefNum|key|))

This field includes the maximum number of permitted authorizations for installment/recurring payments. This field must be > 1(if not empty).

This field includes the frequency for paying the installments and can be any of the following: 'DAILY','WEEKLY','FORTNIGH TLY',’MONTHLY','QUARTERLY', 'HALFYEARLY','YEARLY','ADH OC'

This field includes the indicates the maximum amount which can be debited for each installment/recurring payments i.e., amount to be stored with implied decimals

This field includes the unique reference number used to uniquely identify SI registration and recurring payments

This field includes whether the SI was validated.

This field includes the customer device ID Unique ID that identifies customer device used – IP or Mobile Number or MAC or IMEA

This field captures ctx id, which is unique for every transaction.

This field captures mtx id

For internal use only.

For internal use only.

Merchant can pass any additional data( specific to merchant) not included in the message hash.

This is used to pass DCC or MCP indicator, 1 – DCC indicator 2 – MCP indicator Null/no value – Normal ecommerce transaction

This field can be used to pass any additional data( specific to merchant) not included in the message hash

For internal purposes only.

For internal purposes only.

This parameter must contain the API key provided by Wibmo.