Skip to main content
This guide walks through the full merchant boarding lifecycle — from creating the initial application through compliance checks, e-signature, and final activation. Each step links to the relevant API endpoint or overview for details.

​
Prerequisites

Before you start, you need an API key.
  • API key — Long-lived keys for service-to-service integrations. Pass it as Api-Key <your-api-key> in the Authorization header.

​
Boarding steps

1

Create the application

An application is the merchant application record. All subsequent data — business info, pricing, equipment, and compliance — attaches to this record.Endpoint: Create Application — POST /v1/crm/leadsAt minimum, provide the merchant’s DBA name, legal name, and the agent or ISO the application belongs to. Refer to the Applications Overview for a full description of the application lifecycle and available fields.
2

Add business profile

Populate the merchant’s business details on the application.
  • Address — Add Application Address (POST /v1/crm/leads/{leadId}/addresses). Add the physical business location.
  • Principals — Add Application Principal (POST /v1/crm/leads/{leadId}/principals). Capture each beneficial owner and signer. SSN and date of birth are encrypted at rest.
3

Add banking / deposit information

Provide ACH funding account details so the merchant can receive deposits.Endpoint: Create Application Deposit Info — POST /v1/crm/leads/{leadId}/deposit-infoSensitive bank fields are encrypted. Use Decrypt Application Deposit Info to retrieve them later.
4

Configure pricing

Attach the fee structure that will apply to the merchant after boarding.
  • Pricing package — Create Pricing Package (POST /v1/crm/leads/{leadId}/pricing-packages). Group related fee configurations.
  • Pricing items — Create Pricing Item (POST /v1/crm/leads/{leadId}/pricing-items). Add individual fees such as interchange, basis points, and per-transaction fees.
  • Pricing rules — Create Pricing Rule (POST /v1/crm/leads/{leadId}/pricing-rules). Apply conditional pricing logic if required.
5

Add equipment order (optional)

If the merchant requires physical terminal hardware, create an equipment order on the application.
6

Attach supporting documents

Upload any required underwriting or compliance documents.Endpoint: Create Application Document — POST /v1/crm/leads/{leadId}/documents
7

Send for e-signature

Generate an MPA (Merchant Processing Agreement) signing session for the merchant to review and sign.Endpoint: Create Signing Session — POST /v1/crm/leads/{leadId}/signingOnce the session is created, share the signing URL with the merchant. Use Verify Signing Token to confirm completion.
8

Submit for review

Submit the application to underwriting or compliance for final review.Endpoint: Submit Application for Review — PUT /v1/crm/leads/{leadId}/submit/{reviewer}Pass underwriting or compliance as the reviewer path parameter depending on the required workflow.
9

Transition status through the pipeline

As the review progresses, update the application’s status.Endpoint: Transition Application Status — PUT /v1/crm/leads/{leadId}/transition/{status}See the Applications Overview for a description of available statuses and valid transitions.
10

Retrieve the assigned MID

Once the application is approved and boarding is complete, the merchant is assigned a Merchant ID (MID).Endpoint: Get Application MID — GET /v1/crm/leads/{leadId}/midAt this point the merchant becomes an active client record in the system.

Applications Overview

Full reference for the application lifecycle, status pipeline, and all available sub-resources.

Financial Reporting

Transactions, batches, deposits, and statements for active merchants.