Skip to main content
Version: v1

EIMP

Overview​

EIMP (Enterprise Identity Management Platform) is an internal service leveraged by CCG to retrieve, validate, and manage enterprise customer identities. It acts as the authoritative source for enterprise customer records, ensuring that each customer is uniquely identified and consistently referenced across systems.

Role in CCG Workflows​

  • When a merchant initiates a session, CCG calls EIMP to obtain enterprise customer details.
  • EIMP helps match the incoming customer data to an existing Enterprise ID (EID) or return no results found.
  • This process is transparent to merchants; all EIMP interactions are managed by CCG.

Customer Creation & Update Flow​

  1. Merchant sends customer information to CCG.
  2. CCG calls EIMP to retrieve or validate the enterprise customer record.
  3. If EIMP record is found:
    • If the customer exists in CCG, their information is updated.
    • If not, a new customer and enterprise wallet are created in CCG.
  4. If EIMP record is not found:
    • A local customer is created in CCG, and a local wallet is returned.

Key Considerations​

  • The Customer table in CCG enforces a unique index on enterprise ID to prevent duplicate enterprise customers.
  • If a customer with the same EID exists but is inactive, an exception will occur during creation or update.
  • Merchants do not interact with EIMP directly; all integration is handled by CCG.

Error Handling​

  • If EIMP is unavailable or returns errors, CCG will fall back to creating a local customer record.
  • Proper error handling and validation are essential to maintain data integrity.

APIs​

EIMP provides two main APIs for accessing enterprise customer information:

1. Read API​

  • Use the Read API to fetch customer information by unique identifiers such as hsid or enterpriseId.
  • This is ideal when you already have a specific ID and need to retrieve the corresponding customer record.

2. Search API​

  • Use the Search API to find customers using multiple filters, such as date of birth (dob), name, or other identifiers.
  • This is useful for scenarios where you need to locate a customer but only have partial information or need to search across several fields.

See Also​