SecondSwype is a decline recovery gateway. It never originates a sale of its own — Vrio only ever hands it a transaction that has already been declined somewhere else, and it makes a second attempt at approving it.

That shapes where it fits. A SecondSwype merchant is not attached to a campaign and is not added to a payment router's available merchants, because neither of those is a decline. Instead you place it at one of the two points where Vrio already has a decline in hand:

A checkout decline — as the reattempt merchant on a router's initial decline reattempt, salvaging the sale while the customer is still in checkout.
A renewal decline — as the merchant on a single attempt of a dunning schedule, salvaging a failed subscription renewal.

Both are configured under Setup below.

Supported Functionality

Feature	Supported
Sale	✅
Authorization	❌
Capture	❌
Refund	✅
Void	✅
Card Tokenization	❌
Dynamic Merchant Descriptors	✅
3D Secure	❌
$0 Transactions	❌

Setup

To connect a Merchant using the SecondSwype Gateway,

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

Gateway Details	Description
Security Key*	Campaign security key provided by SecondSwype
Test Mode	Sends every transaction flagged as a test. SecondSwype has no separate sandbox host, so this is how you test against the live endpoint
Pass Merchant Descriptor	Passes the merchant descriptor to SecondSwype with each transaction
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

The two places are configured independently, and the same SecondSwype merchant can serve either one or both.

Recovering an initial decline

Salvages a checkout decline while the customer is still in the checkout process.

Add the SecondSwype merchant as above
Open the router and go to the Advanced Routing tab
Check Reattempt Initial Declined, then Reattempt on a specific Merchant
Select the SecondSwype merchant

See Initial Decline Reattempts for the full set of reattempt options.

Recovering a renewal decline

Salvages a failed subscription renewal as one step of a dunning schedule.

Add the SecondSwype merchant as above
Open the dunning schedule you want to recover through and edit the attempt that should go to SecondSwype
Set that attempt's Merchant to the SecondSwype merchant
Leave Keep Merchant On Success unchecked — it is unavailable for recovery gateways, since a subscription can never keep billing on one

Any attempt that does not name a merchant continues on the merchant of the original attempt, so a subscription recovered through SecondSwype returns to its normal merchant on the next renewal.

Supported Payment Methods

Credit Card

Card Tokenization

SecondSwype does not store cards. Card data is sent on every charge, and the CVV is only sent on the first cycle.

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.

3D Secure

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

Testing

Note : Placing test orders with Test Mode enabled or using SecondSwype 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 SecondSwype for test card information.