Customers
CCG (Convenient Checkout Gateway) creates and manages customer records using multiple identifiers to ensure accurate mapping and a seamless experience across merchants and channels.
important
Customer creation requires at least one primary identifier; if none is provided, the process cannot continue.
Related Documentation
- Customer Creation & Lookup Flow
- Customer Lookup Logic in EIMP
- Enterprise Wallet Upgradation
- Local to Enterprise Wallet Merge
- Wallet Inactivation
🔒 InternalInternal information — not visible in the public (merchant) site.
Types of Customer
- Enterprise Customer: A user with an enterpriseId will have all their payment methods consolidated into a single enterprise wallet, accessible across all merchants. This enables a seamless experience for users who interact with multiple merchants under the same enterprise.
- Local Customer: A user identified only by mcid will have a local wallet, accessible only to the merchant that created it. This is ideal for merchants who want to manage their own customer base independently.
Best Practices
- When upgrading a local wallet to an enterprise wallet, CCG will merge and de-duplicate payment methods to ensure a single, unified wallet per customer. Refer to Wallet Upgrade for more details.
- Regularly review and update merchant configuration to ensure all relevant mcids are supported and mapped correctly.
API Endpoints Supporting Customer Creation
The following API endpoints support customer creation as part of their workflow:
- Sessions:
POST v1/sessions– Initiates a session and creates a customer if needed. - Find Payment Method Search:
POST v1/payment-methods/search– Searches for payment methods and creates a customer if not found. - Payments:
POST v1/payments,POST v1/token/payments– Processes payments and creates a customer if necessary. - Setup Payment Methods:
POST v1/token/setup-payment-methods– Sets up payment methods and creates a customer if required.