Supported Functionality

---

Adding an Ecrypt Merchant

To connect a Merchant using the Ecrypt Gateway,

1. First add Merchant
2. Select Ecrypt as the Gateway
3. Add Gateway Details as outlined below

*Required

Card Tokenization

When Store cards in the Ecrypt vault is checked, Vrio stores the card with Ecrypt after the first approved transaction so that renewals do not have to resend the card details.

How it works:

1. The initial charge is sent with the full card details and is approved as normal.
2. Vrio creates an Ecrypt customer record for the cardholder.
3. Vrio adds the card to that customer's wallet by referencing the approved transaction — the card details are not sent a second time.
4. Renewals charge the stored wallet in a single request.

The customer and wallet identifiers are stored together in the format {ecrypt_customer_id}|{wallet_id}.

---

$0.00 Transactions

Ecrypt cannot charge $0.00, so Vrio sends $0 transactions to the Ecrypt validation endpoint instead. This confirms the card is real and active without charging it, and the result determines whether the transaction is successful.

Unlike gateways that require a $1 authorization and immediate void to validate a card, no charge is ever placed against the card.

Check Bypass $0 Transaction Authorizations to skip the gateway entirely and treat all $0 transactions as successful. The card is not validated when this is checked.

---

3D Secure

Ecrypt does not currently support 3D Secure, either natively or by passing authentication values from a third-party provider. Any 3DS data on the order will not be sent.

---

Request

Required Data Mapping

Below is a table that shows how Vrio maps its data to the Ecrypt API. Values in bold are hard coded values, the rest are dynamic based on the payment.

Auth / Sale (New Card)

Sale is sent to the sale endpoint and Auth to the authorize endpoint. The request body is otherwise identical.

Auth / Sale (Stored Card)

When the card has been stored in the Ecrypt vault, renewals send the stored card instead of the card details.

The order details are passed exactly as they are on a new card transaction.

Capture

Void

Refund

---

Optional Data Mapping

Card Tokenization

If Store cards in the Ecrypt vault is checked, after a successful payment Vrio will create an Ecrypt customer and add the approved transaction's card to that customer's wallet.

Customer

Wallet

The resulting identifiers are stored in the format: {ecrypt_customer_id}|{wallet_id}

---

Response Data Mapping

Below is a table that shows how Vrio maps data from the Ecrypt API response.

Ecrypt returns validation failures in a separate format from declines. When the request itself is rejected — an invalid card number, for example — the response carries an error list rather than a response code, and Vrio maps it as follows.

---

Testing

Note : Placing test orders with an Ecrypt test account or using Ecrypt 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.

Test Cards

To trigger an address match, use 888 as the address and 77777 as the postal code. To trigger a card security code match, use 999 as the CVV. An invalid card number returns a validation error rather than a decline.

---

FAQ

Q: My renewal is sending the full card details instead of using the stored card. Why?

A: Either Store cards in the Ecrypt vault is not checked on the merchant, or the card could not be stored when the initial transaction was processed. Storing the card is deliberately kept separate from taking the payment, so a failure to store it does not decline the transaction — the renewal falls back to sending the card details, which Ecrypt accepts. Check the initial transaction's response data to see whether the card was stored.

Q: My test transaction keeps declining and I do not know why.

A: Ecrypt triggers test declines by amount rather than by card number. Any amount below $1.00 will decline on a US account. Check the amount on the offer before assuming the card or the credentials are at fault.

Q: Does Ecrypt support 3D Secure?

A: No. Ecrypt does not offer 3D Secure and does not accept authentication values from a third-party provider. If 3D Secure is a requirement, use a gateway that supports it.

Q: Which endpoint should I use, Ecrypt or Preferred Payments?

A: Both serve the same API and the same account. Use whichever address the merchant was boarded on — if you are unsure, leave Use Preferred Payments endpoint unchecked.