Supported Functionality

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

Setup

To connect a Merchant using the Tokentech Gateway,

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

Gateway Details	Description
Security Key*	Security key from Tokentech to connect to the gateway
Sandbox	Check this box if these are sandbox credentials.
Processor ID	Processor id to use with Tokentech. When set, it is sent on every request.
Customer Vault Enabled	Check this box when the customer vault is enabled on the Tokentech account.
Bypass $0 Transaction Authorizations	Check this box to bypass card validation with Tokentech 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 set up within the Merchant Account will be passed to Tokentech as `descriptor`.
Pass Additional Merchant Data	When checked, the remaining merchant account data is passed as descriptor fields.
Pass Stored Credentials (CIT/MIT) Data and Billing Method	When checked, stored credential indicators and the billing method are passed with the transaction.
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

When Customer Vault Enabled is checked, charges made with card data ask Tokentech to save the card. Vrio stores the returned vault id and reuses it for every renewal.

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.

3D Secure

Tokentech 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.

Vrio	Tokentech
`order_cardholder_auth`	`cardholder_auth` — `verified` for Y, `attempted` for A
`order_eci`	`eci`
`order_cavv`	`cavv`
`order_xid`	`xid`
`order_3ds_version`	`three_ds_version`
`order_3ds_ds_transaction_id`	`directory_server_id`

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

Testing

Note : Placing test orders with a Tokentech sandbox account or using Tokentech 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 Tokentech for test card information.