Skip to main content

Test scenarios

General information​

We recommend running the test cases before processing real payments. This section provides detailed scenarios that allow you to:

  • verify the correctness and stability of your integration
  • simulate various payment situations to ensure the system is ready to handle real transactions and to prevent potential operational issues

Requirements:​

  1. You have a merchant portal account and an existing test project with API keys.
  2. The test project configured by technical support.
  3. Integration completed.

Direct integration​

Prerequisites for starting the test:

  1. You have a direct integration configured.
  2. A test project with API keys is created and active.
  3. Webhook handling and status‑code processing are set up.
Test caseAction
One-step payments (purchase)One‑stage payment - a payment flow where the full amount is captured from the payer in a single transaction at the time of purchase.
Features:
  1. Charging can be performed using card data (cc_number, exp_month, exp_year, card_cvv) or a token (cc_token).
  2. 3DS verification control.
info

If PCI DSS certification is in place, card data may be submitted in requests.
If PCI DSS certification is not in place, payments must use tokens obtained via the Tokenization widget.

  • Payment by Visa and Mastercard
  1. Create a payment request including cc_number, exp_month, exp_year, card_cvv.
  2. Use test card numbers according to the card brand.
    For example:
    Visa: 4242 4242 4242 4242
    Mastercard: 5454 5454 5454 5454
    The payment may immediately receive a final status of Success, or it may require 3DS/OTP verification. If the response contains "status_description": "3DS verification is required", open the URL in user_action_url and complete the ACS verification by clicking CONFIRM.
  3. Receive the webhook on your server — it will contain the payment status.
  • Payment with 3DS/non‑3DS
  1. Create a payment request with card data and include the order_3ds_bypass parameter.
    Use:
    For 3DS: order_3ds_bypass=always - test card 4242 4242 4242 4242
    Without 3DS: order_3ds_bypass=never - test card 5555 5555 5555 4444
  2. Receive the webhook on your server — it will contain the payment status.

Hosted integration​

Prerequisites for starting the test:

  1. You have a Hosted integration configured.
  2. A test project with API keys has been created and is active.
  3. Webhook handling and status‑code processing are set up.
Test caseAction
One-step payments (purchase)
  1. Create a payment request for 10 XCD.
    A successful request returns an HTTP 303 with a Location header to which the client should be redirected to continue payment.
    Example:
    HTTP/2 303
    # .. other headers
    location: https://api.veloragate.com/api/v1/checkout/1b806782-3d97-4444-abb9-6e4b45d34663/form
  2. Follow the checkout link, fill in all required fields and click “Pay”.
    Checkout view:
  3. The payment may immediately receive a final status of Success, or it may require 3DS/OTP verification. If the response contains "status_description": "3DS verification is required", open the URL in user_action_url and complete the ACS verification by clicking CONFIRM.
  4. Receive the webhook on your server — it will contain the payment status.
  • Payment by Visa and Mastercard
  1. Create a payment request.
  2. Use test card numbers according to the card brand.
    For example:
    Visa: 4242 4242 4242 4242
    Mastercard: 5454 5454 5454 5454
  3. Receive the webhook on your server — it will contain the payment status.
  • Payment with 3DS/non‑3DS
  1. Create a payment request with card data and include the order_3ds_bypass parameter.
    Use:
    For 3DS: order_3ds_bypass=always - test card 4242 4242 4242 4242
    Without 3DS: order_3ds_bypass=never - test card 5555 5555 5555 4444
    Details on using the 3DS protocol
  2. Receive the webhook on your server — it will contain the payment status.