Supported Functionality

Feature	Supported
Authorization	✅
Capture	✅
Refund	✅
Void	✅
Card Tokenization	❌
Dynamic Merchant Descriptors	✅ Trimmed to 25 characters
3D Secure	✅ Pass your own
$0 Transactions	❌

Setup

To connect a Merchant using the Qoin Gateway,

First add Merchant
Select Qoin as the Gateway
Add Gateway Details as outlined below

Gateway Details	Description
Terminal Key*	Terminal Key - provided by Qoin
Bypass $0 Transaction Authorizations	Check this box to bypass card validation with Qoin for $0 transactions. When unchecked, a $1 authorization (voided immediately) will be used to validate the card — the result of this authorization will determine if the transaction is successful. This setting only applies to initial transactions — $0 renewals will always bypass the gateway. Learn more about $0.00 transaction handling.
Pass Merchant Descriptor	When checked, the merchant descriptor setup within the Merchant Account will post to Qoin with the charge details.
Merchant Payment Methods*	The types of payment methods this merchant accepts — credit card only.
Merchant Card Types*	Card types to be accepted on this Merchant
Merchant Default Currency*	Default currency that will be used, if currency is not specified
Merchant Currencies*	All currencies accepted on this merchant

*Required

Supported Payment Methods

Credit Card

Card Tokenization

Qoin does not store cards. Card data is sent on every charge.

Dynamic Merchant Descriptors

When Pass Merchant Descriptor is checked, Vrio sends the Merchant Account descriptor with every charge, or a merchant_descriptor passed when the order is processed, which is then reused for that order's renewals.
If the order later moves to a different merchant, that merchant's descriptor is used instead.
Qoin accepts up to 25 characters and silently shortens anything longer.

3D Secure

Qoin accepts 3D Secure authentication data that you generate with a third party provider. Values are sent whenever authentication data exists on the order for the cycle being charged, and the field names differ by card brand.

Mastercard:

Vrio	Qoin
`order_eci`	`mastercard_authentication.security_level_indicator`
`order_cardholder_auth`	`mastercard_authentication.result`
`order_cavv`	`mastercard_authentication.ucaf_authentication_data`
`order_3ds_version`	`mastercard_authentication.program_protocol`
`order_3ds_ds_transaction_id`	`mastercard_authentication.directory_server_transaction_id`

Every other card brand:

Vrio	Qoin
`order_cardholder_auth`	`card_authentication.result`
`order_cavv`	`card_authentication.cavv`
`order_3ds_ds_transaction_id`, or `order_xid`	`card_authentication.xid`

Nothing is sent unless the authentication result and the CAVV are both present — and for Mastercard, the ECI too.

See Third Party 3DS Providers for the full parameter reference.

Testing

Note : Placing test orders using Qoin test cards will not automatically set the order as a test in Vrio. Be sure to flag the order as a test using the is_test flag after the order is processed. For more details on placing test orders, click here.

Reach out to Qoin for test card information.