Supported Functionality

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

Setup

To connect a Merchant using the Bill1st Gateway,

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

Gateway Details	Description
API Account id*	provided by Bill1st
API Account Password*	provided by Bill1st
One-time Sale Product Code*	provided by Bill1st
One-time Sale Product Code (Auth)*	provided by Bill1st
Rebills Sale Product Code*	provided by Bill1st
Rebills Sale Product Code (Auth)*	provided by Bill1st
Pass AllowNoCVV	Bill1st requires a CVV by default. Check this box to send `AllowNoCVV` on charges made without one.
Pass AllowDuplicateSignup	Check this box to send `AllowDuplicateSignup`, which allows more than one subscription signup to the same site.
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
Bypass $0 Transaction Authorizations	Check this box to bypass card validation with Bill1st for $0 transactions. When unchecked, a $1 authorization (reversed 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

Void

Bill1st has no void operation.
Voiding a transaction in Vrio issues a full credit against the original charge instead.

Card Tokenization

Charges made with card data ask Bill1st to save the card. Vrio stores the returned subscriber id and reuses it for every renewal.

Dynamic Merchant Descriptors

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

3D Secure

Bill1st 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	Bill1st
`order_eci`	`ECIFlag`
`order_cavv`	`CAVV`
`order_xid`	`XID`
`order_cardholder_auth`	`PAResStatus`
`order_3ds_enrollment_status`	`Enrolled`
`order_3ds_version`	`ThreeDSVersion`
`order_3ds_ds_transaction_id`	`DSTransactionId`

The values are collected into a payment object and sent base64 encoded, with the 3DS service set to CARDINAL.

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

Testing

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