Skip to main content

​
Accept payments through Valitor by Rapyd via Vaultera Switch

This section gives you an overview of how to make payments via Valitor by Rapyd through Vautera Switch.
Valitor by Rapyd is a suite of Valitor by Rapyd APIs powering online payment processing and commerce solutions for internet businesses of all sizes. It allows businesses to accept payments and scale faster. To know more about payment methods supported by Valitor by Rapyd via Vaultera Switch visit here.

​
Activating Valitor by Rapyd via Vaultera Switch

​
Prerequisites

  1. You need to be registered with Valitor by Rapyd in order to proceed. In case you aren’t, you can quickly setup your Valitor by Rapyd account here.
  2. You should have a registered Vaultera Switch account. You can access your account from the Vaultera Switch control center→.
  3. The Valitor by Rapyd API key and Account ID are available in your Valitor by Rapyd dashboard under Home page -> Developers -> API credentials.
  4. Select all the payment methods you wish to use Valitor by Rapyd for. Ensure that this is the same as the ones configured on your Valitor by Rapyd dashboard under Settings -> Payment methods
  5. To set webhooks, Navigate to the webhooks section of your Valitor by Rapyd dashboard (Developers -> Webhooks) and create a new standard webhook.
Steps → to activate Valitor by Rapyd on Vaultera switch control center.

​
Authorization

​
API Key Authentication for Valitor by Rapyd via Vaultera Switch

This section provides an overview of how to authenticate API requests using Valitor by Rapyd API Keys through Vaultera Switch.
An API Key is used for authorization. Depending on the setup of a key, different parameters in requests can be optional, required, or not allowed. Therefore, multiple API Keys are provided for different test scenarios and currencies. Please choose the key that corresponds to your use case.

​
Valitor by Rapyd API Key Types

The types provided and their key differences are:

​
Merchant

  • Not allowed to include agreementNumber in requests
  • Not allowed to include terminalId in requests

​
Valitor by Rapyd Test API Keys

Use these Valitor by Rapyd API Keys for Testing The following Valitor by Rapyd test API keys are available for different currencies and scenarios:
These API keys can only be used for testing on our Staging environment.

​
Implementation Guide

​
In Vaultera Dashboard

  1. Navigate to Connectors → Payment processors in the Vaultera Switch control center
  2. Select Valitor by Rapyd as your payment processor
  3. Choose the API key corresponding to your target currency from the table above
  4. Copy the complete API key string
  5. Paste the key into the designated Valitor by Rapyd API Key field

​
Currency Selection Guide

Choose the Valitor by Rapyd API key that matches your testing currency:
  • USD: Use the USD API key for US Dollar transactions via Valitor by Rapyd
  • CAD: Use the CAD API key for Canadian Dollar transactions via Valitor by Rapyd
  • ISK: Use the ISK API key for Icelandic Krona transactions via Valitor by Rapyd
  • GBP: Use the GBP API key for British Pound transactions via Valitor by Rapyd
  • EUR: Use the EUR API key for Euro transactions via Valitor by Rapyd

​
Testing Notes

  • Environment: All Valitor by Rapyd test API keys work only in Staging/Sandbox environment
  • Security: Store Valitor by Rapyd API keys securely and never expose them in client-side code
  • Selection: Choose the Valitor by Rapyd API key that matches your testing currency for proper transaction processing

​
Payment Facilitator

  • API Key: APIKey DemoPF.POED43XUAykXKlHG3GOmdOBSyfb4uuSx2Ft24Kl7uxU=
  • Has multiple submerchants
  • Must include agreementNumber in every request
  • Must include terminalId in every request
  • Must include sponsoredMerchantData object where available

​
Merchant - Multi

  • API Key: APIKey DemoMulti.GJjOqQ3I4PDhIMHyCz6a/5QEcwdF4X3bgJqlBfdCuXM=
  • Single merchant with multiple agreements
  • Must include agreementNumber in every request
  • Must include terminalNumber in every request

​
CardVerification

Returns a 3D Secure HTML document that is used to authenticate the cardholder. Results from the authentication are used when requesting a payment or creating a virtual card. To complete this transaction the HTML form must be presented to the cardholder who must complete the authentication. See the flow chart above. The following table lists the card numbers that may be used during testing to produce different flows in the response. Any expiration date, greater than or equal to the current date, can be used with these cards.

​
Frictionless Flow

CardVerification can give frictionless authentication, meaning that the cardholder does not need to enter any further verification. CardVerification will then return a frictionlessData object that contains all information required to perform an authenticated payment.
Always trigger a challenge when planning to perform a first transaction. Starting a subsequent transaction chain by using a frictionless authentication as a first transaction may be considered insufficient by card issuers resulting in subsequent transactions being rejected.

​
Test Cards - Frictionless Authenticated

​
Method + Frictionless Flow

Frictionless in the sense that the cardholder does not need to enter any further information, but the merchant still needs to redirect the cardholder to perform 3dsMethod. After 3dSMethod is performed then the cardholder will be redirected back to the merchant with the authentication data to perform an authenticated payment.

​
Test Cards - Method + Frictionless Authenticated

​
Challenge Flow

Requires the cardholder to be challenged for authentication, meaning he must be redirected to the card issuer web page where he enters information to verify his identity or confirms via app or cancels. Once challenge is completed, the cardholder will be redirected back to the merchant with data to either perform an authenticated payment or cancel the payment.

​
Test Cards - Challenge Flow

​
Method + Challenge Flow

Cardholder must be redirected to perform 3dSMethod. Method results are that the cardholder must be challenged for authentication which results in a normal challenge flow described above.

​
Test Cards - Method + Challenge Flow