Supported Functionality

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

Setup

To connect a Merchant using the Finix Gateway,

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

Gateway Details	Description
API Key Username*	Your Finix API key username, from Developers > API Keys in the Finix dashboard
API Key Password*	Your Finix API key password, from Developers > API Keys in the Finix dashboard
Merchant ID*	Your Finix Merchant ID, from Finix Processing Details in the Finix dashboard
Use Sandbox Environment	Check to use the Finix sandbox environment for testing
Bypass $0 Transaction Authorizations	Check this box to bypass card validation with Finix 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.
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

Void

Voiding an uncaptured authorization reverses it at Finix.
Once the charge has been captured Finix has no void operation, and Vrio issues a full refund of the original charge instead.

Card Tokenization

Charges made with card data ask Finix to save the card. Vrio stores the returned payment instrument and reuses it for every renewal.

Dynamic Merchant Descriptors

Vrio does not send a descriptor to Finix with the charge, so the customer's statement shows whatever is configured on your Finix account.

3D Secure

Finix 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	Finix
`order_cavv`	`3d_secure_authentication.cardholder_authentication`
`order_eci`	`3d_secure_authentication.electronic_commerce_indicator`
`order_3ds_ds_transaction_id`, or `order_xid`	`3d_secure_authentication.transaction_id`

All three must be present. If any one is missing, no authentication data is sent.

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

Common Errors

A transaction returns PENDING and is treated as a decline

Finix returns a state on every authorization and transfer. Vrio only treats SUCCEEDED as a successful transaction — per Finix's documentation, PENDING means the transaction is still processing and may yet resolve to FAILED, so it is not counted as an approval.

Testing

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

For Finix test cards, check here.