Supported Functionality

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

Setup

To connect a Merchant using the Fluid Pay Gateway,

First add Merchant
Select Fluid Pay as the Gateway
Add Gateway Details as outlined below

Gateway Details	Description
API Key	API Key provided by Fluid Pay
Processor ID	Designates a specific processor for the transaction. If no value is provided, the transaction will run against the default processor set on your gateway. If no value is provided and there is no default set, the transaction will fail.
Vendor ID	Vendor ID passed along to certain processors, if supported (Special Field, only use if instructed by support)
Sandbox	When checked, this merchant should use Sandbox credentials and sandbox endpoint
Pass Merchant Descriptor	When checked, the merchant descriptor set on the Merchant Account is sent to Fluid Pay with the charge. See Dynamic Merchant Descriptors.
Pass Additional Descriptor Data	Only applies when Pass Merchant Descriptor is checked. Sends the Merchant Account address, city, state and postal code with the descriptor as well. Fluid Pay accepts 38 characters for the address, 21 for the city, 2 for the state and 5 for the postal code, and anything longer is shortened.
Bypass $0 Transaction Authorizations	Check this box to bypass card validation with Fluid Pay 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

Card Tokenization

Charges made with card data ask Fluid Pay to save the card. Vrio stores the returned vault record 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.
Fluid Pay accepts up to 38 characters and silently shortens anything longer.

3D Secure

Fluid Pay 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	Fluid Pay
`order_eci`	`eci`
`order_cavv`	`cavv`
`order_xid`	`xid`
`order_3ds_version`	`version`
`order_3ds_ds_transaction_id`	`ds_transaction_id`

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

Common Errors

Forbidden error: User is not permitted to perform this action

The Fluid Pay account does not have permission to create vault records. Vrio asks Fluid Pay to vault the card on every sale and authorization, so the whole charge fails. Have Fluid Pay enable vault permissions on the account.

Testing

Note : Placing test orders with a Fluid Pay sandbox account or using Fluid Pay 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 Fluid Pay test cards, check here.