Skip to main content

Merchant Integration Flow

This page outlines the step-by-step process for integrating merchants with our Enovipay platform (Spell) across three main integration types: Direct API, Direct CRM/Cashier, and Indirect CRM/Cashier via Payment Bridge.

Updated over 2 weeks ago

1. Direct API Integration

  1. Merchant Account Setup

    • Merchant must have an active account registered on our Enovipay merchant platform (Spell).

  2. Credential Sharing

    • Share all necessary account credentials with the merchant.

  3. Documentation Provision

    • Provide the merchant with the complete API documentation.

  4. Key Provision and Explanation

    • Share the API Key and Brand ID with the merchant.

    • Explain the process for retrieving these from the merchant portal.

  5. Webhook Configuration

    • Explain the webhook configuration process.

  6. PCI DSS Compliance (If Applicable)

    • If the merchant is PCI DSS Compliant, review the merchant certification.

    • Provide the merchant with the Server-to-Server (s2s) token.

2. Direct CRM or Cashier Integration (e.g., Paymid)

  1. Solution Request

    • Merchant must request the enabling of our solution for their account from the provider.

  2. Merchant Account Setup

    • Merchant must have an active account registered on our platform (Spell).

  3. Credential Sharing

    • Share all necessary account credentials with the merchant.

  4. Documentation Provision

    • Provide the merchant with the complete API documentation.

  5. Key Provision and Explanation

    • Share the API Key and Brand ID with the merchant.

    • Explain the process for retrieving these from the merchant portal.

  6. Webhook Configuration

    • Explain the webhook configuration process.

  7. PCI DSS Compliance (If Applicable)

    • If the CRM or Cashier is PCI DSS Compliant, obtain and share the certification.

    • Provide the merchant with the Server-to-Server (s2s) token.

  8. Management Dashboard Connection

    • Merchant must connect to our solution through their management dashboard by submitting the shared credentials.

3. Indirect CRM or Cashier Integration via Payment Bridge (e.g., PIQ)

  1. Connector Request

    • Merchant must request the enabling of our Payadmit connector for their account from the provider.

  2. Merchant Account Setup

    • Merchant must have an active account registered on our platform (Spell).

  3. Payadmit Key Generation

    • Generate the API and signing keys required for Server-to-Server (s2s) and Hosted Payment Page (HPP) Payadmit integration.

  4. Key Sharing

    • Share these generated keys with the merchant.

  5. Management Dashboard Connection

    • Merchant must connect to our solution through their management dashboard by submitting the shared credentials.

For any questions or further clarifications, please contact the tech team.

Did this answer your question?