Fluidpay is a standard gateway integration.

Vrio will always try and tokenize the card when processing a Sale or an Auth by passing the following in the request:

create_vault_record=true

Supported Functionality

✅ Authorize Payments
✅ Refund Payments
❌ Accepts $0 Transactions
❌ ACH Support
❌ Digital Wallet Support
✅ Capture Payments
✅ 3DS Support
✅ Card Tokenization
❌ CVV Required

Adding a FluidPay Merchant

To connect a Merchant using FluidPay Gateway,

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

Gateway Details	Description
API Key	API Key provided by FluidPay
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
Bypass $0 transaction authorizations	The FluidPay 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.
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.

DataAction=token/add

amount	Transaction Total
tax_amount	Transaction Tax
shipping_amount	Transaction Shipping
currency	Transaction Currency
order_id	Transaction ID
ip_address	IP Address
email_address	Customer Email Address
processor_id	value set on merchant for Processor ID
vendor_id	value set on merchant for Vendor ID
Initial Sales ( Not Recurring )
billing_method	straight
Initial Sales ( Recurring )
billing_method	initial_recurring
Recurring Sales ( Sublytics Transaction Cycle > 1 )
billing_method	recurring
Payment Method (If Token )
payment_method.customer.id	Customer Card Merchant Token ( customer_id from original response )
payment_method.customer.payment_method_id	Customer Card Merchant Token ( response.card.id from original response )
payment_method.customer.payment_type	card
Payment Method ( If No Token )
payment_method.entry_type	keyed
payment_method.cvc	Customer Card CVV ( if present )
payment_method.number	Customer Card Number
payment_method.expiration_date	Customer Card Expiration Month / Customer Card Expiration Year
3DS Information ( If available )
payment_method.cardholder_authentication.eci	Transaction ECI
payment_method.cardholder_authentication.cavv	Transaction CAVV
payment_method.cardholder_authentication.xid	Transaction XID
payment_method.cardholder_authentication.version	Transaction 3ds Version
payment_method.cardholder_authentication.ds_transaction_id	Transaction 3ds Transaction ID ( version 2+)
Billing / Shipping Information
billing_address.first_name	Billing First Name
billing_address.last_name	Billing Last Name
billing_address.company	Billing Organization
billing_address.email	Billing email
billing_address.phone	Billing Telephone
billing_address.address_line_1	Billing Address Line 1
billing_address.address_line_2	Billing Address Line 2
billing_address.city	Billing City
billing_address.state	Billing State
billing_address.postal_code	Billing Postal Code
billing_address.country	Billing Country
shipping_address.first_name	Shipping First Name
shipping_address.last_name	Shipping Last Name
shipping_address.company	Shipping Organization
shipping_address.email	Shipping email
shipping_address.phone	Shipping Telephone
shipping_address.address_line_1	Shipping Address Line 1
shipping_address.address_line_2	Shipping Address Line 2
shipping_address.city	Shipping City
shipping_address.state	Shipping State
shipping_address.postal_code	Shipping Postal Code
shipping_address.country	Shipping Country

Response Data Mapping

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

FluidPay	Vrio
id	Gateway Response ID ( used for refunds / voids )
order_id	Gateway Response Gateway ID ( not currently used)
response_code	Gateway Response Code
response_body.card.auth_code	Gateway Auth Code
response_body.card.cvv_response_code	Gateway Response CVV Code
response_body.card.avs_response_code	Gateway Response AVS Code
msg	Processor Response Text
customer_id\|customer_payment_ID	Customer Card Merchant Token

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 FluidPay 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 FluidPay Portal.
Follow full transaction testing and validation steps here.

Common Errors

Error: Forbidden error: User is not permitted to perform this action

Cause: The account doesn't have permission to create vault records which is what was causing the error

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.

Reach out to Fluid Pay for test card information.