Supported Functionality

Feature	Supported
Authorization	✅
Capture	✅
Refund	✅
Void	✅
Card Tokenization	✅
Dynamic Merchant Descriptors	❌
3D Secure	✅ Pass your own or gateway-managed
$0 Transactions	✅

Setup

To connect a Merchant using the Worldnet Gateway,

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

Gateway Details	Description
API Key*	Merchant API Key from Worldnet SelfCare
Terminal Number*	Terminal number assigned by Worldnet
Sandbox	Check this box if these are sandbox credentials. When checked, requests are sent to the Worldnet sandbox environment.
Bypass $0 Transaction Authorizations	Worldnet has a card verify endpoint for $0 transactions, which Vrio uses to validate the card. Check this box to bypass the gateway entirely for $0 transactions. This setting only applies to initial transactions — $0 renewals will always bypass the gateway. Learn more about $0.00 transaction handling.
Pass MOTO Channel	Check this box to send transactions on the MOTO channel instead of WEB.
Attempt 3D Secure	Check this box to attempt Worldnet-managed 3D Secure authentication through Worldnet MPI.
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 Worldnet to save the card. Vrio stores the returned secure credentials and reuses them for every renewal.

Dynamic Merchant Descriptors

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

3D Secure

When Attempt 3D Secure is checked and a redirect_url is present on the order, Worldnet MPI performs the authentication.

Vrio sends the payment request without any third-party 3DS values.
If Worldnet returns a redirect link, Vrio returns a response_code: 101 with that URL in the post_data field — the customer is redirected to complete 3DS authentication.
If no redirect is returned, the payment is processed in a single step.
After the customer completes authentication and is redirected back, the checkout calls the /order/{order_id}/complete endpoint. Vrio retrieves the payment and completes the transaction when its status is READY, PENDING or COMPLETE.

For handling the 101 response code, see Handling 101 Response Codes.

🚧
Third Party 3DS Providers
When Attempt 3D Secure is checked and a redirect URL is present, Worldnet-managed authentication is used and any third-party 3DS values passed on the order are not sent. To pass your own 3DS values, leave Attempt 3D Secure unchecked. Learn more about third-party 3DS integrations here.

Passing your own values

Worldnet also accepts 3D Secure authentication data that you generate with a third party provider. When those values are present on the order they are sent with the charge and Worldnet does not run its own authentication.

Vrio	Worldnet
`order_eci`	`threeDSecure.eci` — `FULLY_AUTHENTICATED` for ECI 05 or 02, otherwise `ATTEMPTED_AUTHENTICATION`
`order_cavv`	`threeDSecure.cavv`
`order_xid`	`threeDSecure.xid`
`order_3ds_version`	`threeDSecure.protocolVersion`
`order_3ds_ds_transaction_id`	`threeDSecure.dsTransactionId`

The service provider is sent as THIRD_PARTY.

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

MOTO

When Pass MOTO Channel is checked, transactions are sent with channel: MOTO. When unchecked, transactions are sent with channel: WEB.

📘
3D Secure takes priority
MOTO describes an order taken while the cardholder is not present, and 3D Secure authenticates a cardholder who is, so the two describe opposite transactions. When an authentication is actually being attempted, Vrio leaves MOTO off.
That covers both ways a transaction gets authenticated: Attempt 3D Secure running on an order processed with a redirect_url, and third party authentication data present on the order as described in Passing your own values. Worldnet only authenticates on the WEB channel, so those transactions are sent with channel: WEB. Everything else with the box checked is sent with channel: MOTO.

Testing

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