Skip to main content
Ecommpay is a global payments company that helps online businesses accept and manage payments. It operates in multiple regions and industries, providing a platform for merchants and payment service providers.

​
Setup

Contact Ecommpay to obtain sandbox credentials for your region. Then, in the Gr4vy dashboard, add your Ecommpay connection using your Project ID and Secret key.

​
Connector configuration

After setting up your Ecommpay connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:
  • Using Flow - Configure Ecommpay as the target connector in Flow to automatically route card transactions to this connector
  • Using the API - Explicitly set the payment_service_id parameter to the Ecommpay connector ID when creating transactions. This overrides any Flow routing rules.
The connector ID can be found in the dashboard under Connections -> Configured connections.

​
Tokenization callbacks

Your Ecommpay contact must enable tokenization for your project. After it is enabled, set up a dedicated tokenization callback. Gr4vy automatically handles Ecommpay’s transaction webhooks, but tokenization results use a separate callback. To configure the tokenization callback:
  1. In the Ecommpay dashboard, go to Settings -> Callbacks.
  2. Create a new callback using the synchronization URL from your Ecommpay connector settings in the Gr4vy dashboard.
  3. Set the callback result type to “tokenize.”

​
Credentials

When setting up Ecommpay in the dashboard, configure the following credentials.
  • Project ID - The numeric project identifier from your Ecommpay dashboard.
  • Secret key - The secret key from your Ecommpay dashboard.

​
Capabilities

​
Supported countries

​
Supported currencies

​
Limitations

  • Asynchronous processing - Ecommpay acknowledges requests immediately and completes transactions asynchronously. Gr4vy polls for status updates after the initial call, sending up to three checks at roughly the 1, 3, and 5 second marks. Webhooks are monitored as a fail-safe. One transaction can appear as multiple API requests plus a webhook event in the dashboard.
  • CVV required - A CVV is required for all card payments, except for stored credential follow-up payments and merchant-initiated transactions where the initial payment included a CVV.
  • Closed loop - Ecommpay can only process card tokens generated through Ecommpay.
  • 3DS required - Ecommpay requires 3D Secure (3DS) authentication for all card payments. Use Gr4vy hosted 3DS to satisfy this requirement.
This is a closed-loop connector. Some failover scenarios are limited. For details, see Open-loop versus closed-loop.

​
Integration

To accept card payments with Ecommpay, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which routes the payment to your configured Ecommpay connection based on your Flow rules or explicit payment_service_id parameter.

​
Required fields

Ecommpay requires the following fields in the billing_details of a card payment:
  • Email address - Required for checkout.
  • Phone number - Required for checkout.

​
Payouts (travel MCC)

The Gr4vy integration supports payouts for travel-related merchant category codes when enabled for your Ecommpay account. For setup details and API usage, see the Payouts overview.