Supported Functionality

Feature	Supported
Authorization	✅
Capture	✅
Refund	✅
Void	✅
Card Tokenization	✅
Dynamic Merchant Descriptors	✅ Requires `PREFIX*DETAIL` format
3D Secure	❌
$0 Transactions	❌

Setup

To connect a Merchant using the PayNetworx Gateway,

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

Gateway Details	Description
API Username*	provided by PayNetworx
API Password*	provided by PayNetworx
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
Pass Merchant Descriptor	When checked, the merchant descriptor set on the Merchant Account is sent to PayNetworx with the charge. PayNetworx requires the descriptor in two parts — see Dynamic Merchant Descriptors.
Bypass $0 Transaction Authorizations	Check this box to bypass card validation with PayNetworx 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.

*Required

Supported Payment Methods

Credit Card

Card Tokenization

Charges made with card data ask PayNetworx to save the card. Vrio stores the returned token 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.

PayNetworx takes it as two values, so the descriptor must be written as PREFIX*DETAIL — Vrio splits on the asterisk, and the prefix must be 3 to 7 characters with the detail 14 or fewer.
A descriptor that does not match is not sent at all, even with the box checked.

Descriptor	Sent to PayNetworx
`1234*ABCDEFG`	Prefix `1234`, Detail `ABCDEFG`
`12*1234`	Nothing — the prefix is under 3 characters
`1234ABCDEFG`	Nothing — there is no asterisk

3D Secure

PayNetworx does not accept 3D Secure authentication data. Authentication values passed with an order are not sent to the gateway.

Testing

Note : Placing test orders using PayNetworx 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 PayNetworx for test card information.