DocsSDKsAPI
Dashboard

Configuring Acquirer Details

Acquirer configuration is required for production 3D-Secure authentications. While acquirer details are not needed when testing in Sandbox, you must configure them before processing live transactions.

When you process 3D-Secure authentications in production, the card networks require information about your payment acquirer (the bank or payment processor that handles your card transactions). This acquirer information is necessary for the authentication process to work correctly.

Evervault provides two ways to manage your acquirer details:

Configure Acquirer Details Once

The recommended approach is to configure your acquirer details once using the Evervault Acquirers API. This allows you to store your acquirer configurations securely and reuse them across all your 3D-Secure sessions without needing to pass these details with every API request.

Benefits of pre-configuring acquirer details:

  • Simplified integration: No need to include acquirer details in every 3DS session creation request
  • Better security: Acquirer details are stored securely and not exposed in your application code
  • Easier management: Update acquirer details in one place when your payment processor changes
  • Multi-network support: Configure different acquirer details for each card network (Visa, Mastercard, etc.)

Setting Up Default Acquirer Configurations

You can configure a default acquirer for each card network (Visa, Mastercard, American Express). When creating a 3DS session, Evervault will automatically use the appropriate acquirer configuration based on the card network.

You can use the REST API to configure your acquirer details for production. Of note, configurations are stored per app_id, so you will need to configure these for your sandbox and production app separately.

Provide Acquirer Details Per Request

Alternatively, you can provide acquirer details directly when creating each 3DS session by including the acquirer object in your API request. This approach is useful if you work with multiple acquirers or need to specify different acquirer details for different transactions.

Note that supplying acquirer details per request adds complexity to your integration. You'll likely need to perform a BIN lookup to identify the card network, so that you can then decide which acquirer BIN/MID values to provide for that specific transaction.

How Evervault Resolves Acquirer Details

When you create a 3DS session, Evervault determines which acquirer configuration to use in the following order:

  1. Explicit acquirer details: If your request includes a complete acquirer object, those details will be used
  2. Configured acquirer reference: If your request includes an acquirer_id string in the acquirer field, we'll use that specific configuration
  3. Default acquirer: If no acquirer details are provided in the request, we'll automatically use the default acquirer configuration for the card's network, if available
  4. No configuration found: If no acquirer details can be resolved, the session creation will fail

Moving from Sandbox to Production

When you're ready to move from testing to production:

  1. Complete your sandbox testing using the test cards and flows available in Sandbox mode
  2. Setup your acquirers using the Rest API to:
    • Configure your acquirer details for each card network you'll support
  3. Update your app credentials to use your production App ID and API key
  4. Test with small transactions to verify everything works correctly in production

Your integration code doesn't need to change when moving to production—if you've configured your acquirer details with Evervault, they'll be automatically applied to your live 3DS sessions.