Supported Functionality

Adding a Qoin Merchant

To connect a Merchant using 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	The Qoin gateway will decline $0 sales. Vrio will run a $1 authorization (and void it immediately) for $0 sale transactions, the authorization request will determine if the sale is successful. When Checked - Vrio will bypass any $0 transaction, no attempt will be made at the gateway, and treat all $0 transactions as successful.
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

Request Data Mapping

Below is a table that will show how Vrio maps its data to the requested payment gateway API. Values in bold are hard coded values, the rest are dynamic based on the payment.

Qoin	Vrio
user_id	Merchant user id setting
order.order_id	Transaction Id
amount	Transaction Total
currency	Transaction Currency Code
source_ip_address	Ip Address
email	Billing Email
phone_number	Billing Phone
account.first_name	Billing First Name
account.last_name	Billing Last Name
account.billing_address.address_1	Billing Address Line 1
account.billing_address.address_2	Billing Address Line 2
account.billing_address.city	Billing City
account.billing_address.state	Billing State
account.billing_address.postal_code	Billing Postal Code
account.billing_address.country_code	Billing Country
descriptor	Merchant Descriptor
If Vrio Offer Type = recurring offer
credential_on_file.type	recurring
credential_on_file.initiated_by	merchant if cycle > 1 else customer
Payment Method (if card passed)
account.card_number	Customer Card Number
account.expiry_year	Customer Card Expiration Year
account.expiry_month	Customer Card Expiration Month
account.card_security_code	Customer Card CVV ( if present )
For Recurring Sales
url endpoint	/`{payment_id}`/rebill where payment_id is the initial payment id on that order

Response Data Mapping

Below is a table that will show how Vrio maps its data in the API response.

Qoin	Vrio
payment_id	Gateway Response ID ( used for refunds / voids )
transaction_id	Gateway Response Gateway ID
processor.approval_code	Gateway Auth Code
processor.avs	Gateway Response CVV Code
processor.cvv	Gateway Response AVS Code
processor.message	Processor Response Text
code	Code
message	Message

Testing Capabilities and Results

What we can / cannot test for based on the gateway’s sandbox and test card capabilities.

Testing Tips

When testing Gateways, ensure to use the Qoin test cards to test through to the Gateway.
Vrio recommends placing multiple test scenarios, confirming in the Vrio Gateway API Log what data is passed.
Then confirm within the Qoin Portal.
Follow full transaction testing and validation steps here.

Test Card Payment Info:

Please request test information from Qoin directly.

Testing Simulations

Approval/Decline: Amount > 25.00 & Amount < 45.00 code = insufficient_funds

Amount < 15.00 code = insufficient_funds

Amount > 100.00 code = amount_above_limit

Otherwise code = approval

Testing Capability	Available
Auth	Y
Capture	Y
Auth & Capture	Y
One Time Sales	Y
Recurring Sale	Y
$0 Transaction	N ( if Bypass $0 transaction authorizations, we will always return this response Successful zero $type, gateway was bypassed.), if its not, we will attempt a $1 auth and return the response from that
Decline	Y
Voids	Y
Refunds	Y
3DS	X