Supported Functionality

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

Setup

To connect a Merchant using the Payarc Gateway,

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

Gateway Details	Description
Bearer Token*	Bearer Token from the Payarc dashboard, sent as the `Authorization: Bearer` header.
Sandbox Mode	Check this box if these are sandbox credentials. When checked, requests are sent to the Payarc sandbox environment.
Pass Merchant Descriptor	When checked, the merchant descriptor set up within the Merchant Account will be passed to Payarc as `statement_description`.
Bypass $0 Transaction Authorizations	Check this box to bypass card validation with Payarc 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 Payarc to save the card. Vrio stores the returned card 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.
Payarc accepts up to 25 characters and silently shortens anything longer.

3D Secure

Payarc 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	Payarc
`order_cavv`	`secure_code`
`order_eci`	`eci_indicator`
`order_3ds_ds_transaction_id`	`directory_server_transaction_id`

Values are sent on charges where card data is passed, when a cardholder authentication status is present on the order.

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

Testing

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