Test Connector Sandbox

Test your payment and payout integrations in a safe sandbox environment. Set up your test accounts and start building with ValoraPay.

Test Connector Documentation

The Test Connector allows you to test payment and payout flows in a sandbox environment. Set up your merchant and provider accounts to start testing your integration with ValoraPay.

Set up Account H2H merchant account

Step 1: Create Merchant Account

To create an account send connection request at the provider's website or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials

Credentials that have to be issued:

  • Merchant ID
  • API Key
  • Currency settings (You can set these parameters according to available currencies and features for your wallets and services, but it's necessary to check details of the connection with your ValoraPay account manager.)

Connect Merchant Account

Step 1. Connect H2H account at the ValoraPay Dashboard

  1. Go to the Provider Hub page in 'New connection' section and choose H2H Merchant account option to open Connection form.
  2. Enter credentials:
    • Merchant ID
    • API Key
    • Currency settings
  3. Click Connect to complete the setup.

Success! You have connected Test H2H merchant account!

API Examples

Minimum data set to create a payment invoice

SALE
{
  "amount": 100,
  "currency": "USD",
  "customer": {
    "email": "customer@example.com"
  }
}

Maximum data set to create a payment invoice

SALE
{
  "amount": 100,
  "currency": "USD",
  "customer": {
    "first_name": "John",
    "last_name": "Doe",
    "email": "customer@example.com",
    "phone": "+1234567890",
    "address": {
      "country": "US",
      "state": "NY",
      "city": "New York",
      "address": "123 Main St",
      "post_code": "10001"
    }
  },
  "metadata": {
    "product_name": "Test Product",
    "product_type": "digital"
  }
}

Minimum data set to create a payout invoice

PAYOUT
{
  "amount": 100,
  "currency": "USD",
  "customer": {
    "email": "recipient@example.com"
  }
}

Maximum data set to create a payout invoice

PAYOUT
{
  "amount": 100,
  "currency": "USD",
  "customer": {
    "first_name": "Jane",
    "last_name": "Smith",
    "email": "recipient@example.com",
    "phone": "+1234567890",
    "address": {
      "country": "US",
      "state": "CA",
      "city": "Los Angeles",
      "address": "456 Oak Ave",
      "post_code": "90001"
    }
  }
}

Constants

If some parameters are not sent in the transaction creation request, they will take the values from the set constants.

ConstantParameter
FIRST_NAMEcustomer [first_name]
LAST_NAMEcustomer [last_name]
CARDHOLDER_NAMEcustomer [cardholder_name]
COUNTRYcustomer [address] [country]
STATEcustomer [address] [state]
CITYcustomer [address] [city]
ADDRESScustomer [address] [address]
STREETcustomer [address] [street]
POST_CODEcustomer [address] [post_code]
EMAILcustomer [email]
PHONEcustomer [phone]
DATE_OF_BIRTHcustomer [date_of_birth]
BIRTH_DATEcustomer [birth_date] ?? constants [birth_date]
FULL_ADDRESScustomer [address] [full_address]
REGIONcustomer [address] [region]
PAYER_MIDDLE_NAMEcustomer [address] [middle_name]
PAYER_ZIPcustomer [address] [zip]
TERM_URL_TARGETcustomer [address] [url_target]
CUSTOMER_REFERENCE_IDcustomer [customer_reference_id] ?? constants [customer_reference_id]
ProductNamemetadata [product_name]
ProductTypemetadata [product_type]
IPconstant [ip]
LANGconstant [lang]
REASONconstant [reason]
SERVICEGROUPconstant [service_group]
TAXCLASSconstant [tax_class]
VARIANTconstant [variant]
USER_DEVICEconstants [user_device]
USER_AGENTconstants [user_agent]
PAYMENT_PURPOSEcustomer [metadata] [payment_purpose] ?? constants [payment_purpose]
NATIONAL_IDcustomer [national_id] ?? constants [national_id]
OSconstant [os]
OS_VERSIONconstant [os_version]
IS_MOBILEconstant [is_mobile]
PLUGINSconstant [plugins]
INDIVIDUAL_TAX_IDcustomer [individual_tax_id]
PASSPORT_NUMBERcustomer [passport_number] ?? constants [passport_number]

Provider Options

Ignore callback

For cascading to work correctly, we exclude the possibility of finalizing payments using asynchronous callbacks, ignore the callback, do not change the status of the transaction on it in any way and rely only on the status request for finalization (Reconciliation).

Enable reconciliation for 3DS

Enable this option to use reconciliation for 3D Secure transactions.

Default Values

If some parameters are not passed in the request to create a transaction and the corresponding constants have no values, then default values will be passed instead.

ParameterDefault Value
TEST_TEST'192.168.0.1'
TEST_TEST'_test'

Still looking for help connecting your Test account?

Please contact our support team!

Contact Support