Create a New Debit Primary Card [New Client]

This diagram illustrates the sequence of API calls needed to request a new primary debit card for a first-time client.

Option 1

Option 1 involves using a single API to create the client, account, and card.

Create New Primary Debit Card [New Client]

Option 1

User

Issuer App

Issuer Middleware

Network

Option 2

Option 2 involves using three separate APIs to create the client, account, and card.

Create New Primary Debit Card [New Client]

Option 2

User

Issuer App

Issuer Middleware

Network

Process: Create New Primary Debit Card for a New Client

1. User Initiates a Debit Card Request
   • The user initiates a request to obtain a new debit card by interacting with the Issuer App.
   • The Issuer App prompts the user to enter their details and select the desired debit card product.
2. User Provides Information
   • The user fills in their personal details, addresses, ID proof document... as required and submits the request to the Issuer App.
3. Request Processing by the Issuer App
   • The Issuer App forwards the submitted request to the Issuer Middleware for further processing.
4. Issuer Middleware Acknowledges Receipt
   • The Issuer Middleware confirms the receipt of the request and sends an acknowledgment back to the Issuer App.
   • The Issuer App then informs the user that the request has been successfully received.
5. Middleware Reviews and Processes the Request
   • The Issuer Middleware reviews the request details, perform mandatory compliance checks:
     1. KYC (Know Your Customer) Verification: Validates the user's identity, residency, and financial background.
     2. Name Screening: Checks the user’s name against watchlists, sanctions list, and politically exposed persons (PEP) databases.
     • If the KYC and name screening checks pass, the process continues. Otherwise, the request is flagged.
6. Issuer Middleware Initiate the Process
   • The issuer initiates the process of generating a new client number, or as part of client create API. NI can generate it and return it in the response.
7. Client Boarding
   • Option 1 Approach which consolidates the process into a single call to create the client, account, and card using the Endpoint: POST /onboarding/client/private/debit.
   • Once NI receives the request, it will be processed, and upon successful creation of the client, account, and card, a 201 HTTP response will be returned. If you receive a different response, you will need to correct the request and resend it.
8. Client Creation
   • Option 2 Approach You can also replace step 7 by steps 8, 9, and 10
   • The Issuer Middleware sends a POST request to NI to create a new client record:
     Endpoint: POST /clients/private
   • The NI service processes the request and returns a 201 HTTP response, confirming the successful creation of the client. If you have got different response, then you need to fix the request and send it again.
9. Account Creation
   • The Issuer Middleware sends another POST request to NI to create an account
     Endpoint: POST /accounts/private/debit
   • The NI service successfully creates the account and returns a 201 HTTP response. If you have got different response, then you need to fix the request and send it again.
10. Primary Debit Card Issuance
    • The Issuer Middleware sends a POST request to NI to generate and issue a primary debit card for the client:
      Endpoint: POST /cards/primary
    • The NI service successfully creates the debit card and returns a 201 HTTP response. If you receive a different response, then you need to fix the request and send it again.
11. Client Boarding
    • You can also replace steps 7, 8, and 9 with the Option 2 approach, which consolidates the process into a single call to create the client, account, and card using the Endpoint: POST /onboarding/client/private/debit.
    • Once NI receives the request, it will be processed, and upon successful creation of the client, account, and card, a 201 HTTP response will be returned. If you receive a different response, you will need to correct the request and resend it.
      Note: If any part of the request fails, the entire request will be rejected.
12. Middleware Completes Processing
    • Once all operations (client, account, and card creation) are successfully completed, the Issuer Middleware returns a response to the Issuer App.
13. User Notification
    • The Issuer App receives the response from the Issuer Middleware.
    • The Issuer App then notifies the user about the final status of their debit card request.