DgPaysDgPaysEverest Card
Sign in

Journey 01

Launching a new card

From an empty portfolio to live, transacting cards. Pick your product line — the platform pattern is the same: authenticate, configure, issue, activate, transact.

Sections3Steps15Calls19Gaps6

You do this once per product line. This journey is split by product line.

Pick a section

The sections below are independent — open the one you are working on. The steps inside a section run in the order they are listed.

Credit

APIs
OAuth2Common MethodsCredit DC
Capabilities
AuthenticationCustomersCard issuance and personalisationCard lifecyclePIN and card securityTransactions

  1. Get an access token

    Authenticate with client credentials against the Security Token Service. Every later call carries this bearer token; scopes control what it can do.

    access_tokenuse in the Authorization header

  2. Register the customer

    One-time registration of the core-banking customer with Everest. Idempotent — safe to repeat.

    customerNumberconfirmed

  3. Choose the product

    List the credit products this customer is eligible for, by the customer number the previous step confirmed. Present only those.

    productNumbercarries into issuance

    Product parameters are not readableNo operation reads a product's configuration. Limit parameters are readable, which is a different thing.

  4. Issue the card

    One call creates the card: product, limit, linked settlement account, statement day, delivery and initial permissions. Add a virtual companion card for instant online spend before the plastic arrives. The call returns when the card record exists — the physical card is four stages away and none of them is yours to drive.

    shadowCardNumbersave it — every later call needs it

    The production chain is not an APIBetween the card record being created and the cardholder holding it there are four more stages — generation, embossing, personalisation and despatch — and none of them is an operation you call. Embossing in particular runs as a batch: requests accumulate through the day and go to the production bureau in one session, which is why the only published calls around it read the pending list and cancel from it. Delivery is the stage that does come back: the courier file, the movements and the barcode are all callable.

  5. Activate and set the PIN

    After delivery (instant in Sandbox), activate and set the PIN with an encrypted PIN block.

    statusA — active

  6. Post the first transaction

    Quote the fee, post a payment in Sandbox, and read it back from current-period history.

    utidpersist against your ledger entry

Debit

APIs
OAuth2Debit DCCredit DC
Capabilities
AuthenticationCard issuance and personalisationAccount linkingCard lifecyclePIN and card securityTransactions

  1. Get an access token

    Same STS, debit scopes.

    access_tokenready

  2. Issue against accounts

    Create the debit card linked to one or more deposit accounts; the first is the default settlement account.

    shadowCardNumberof the debit card

    The production chain is not an APIBetween the card record being created and the cardholder holding it there are four more stages — generation, embossing, personalisation and despatch — and none of them is an operation you call. Embossing in particular runs as a batch: requests accumulate through the day and go to the production bureau in one session, which is why the only published calls around it read the pending list and cancel from it. Delivery is the stage that does come back: the courier file, the movements and the barcode are all callable.

  3. Link more accounts

    Attach additional accounts and set the selection priority customers see at ATM and POS.

    priorityorder confirmed

  4. Activate, PIN, transact

    Activation and PIN services are shared across product lines. Then read debit activity — on-us and off-us.

    statusA — active

Prepaid

APIs
OAuth2Prepaid DC
Capabilities
AuthenticationCard issuance and personalisationNo-name cards

  1. Get an access token

    Same STS, prepaid scopes.

    access_tokenready

  2. Issue from stock

    Activate anonymous no-name stock by barcode or issue named cards singly. Anonymous cards carry regulatory caps until registered.

    shadowCardNumberof the prepaid card

    The production chain is not an APIBetween the card record being created and the cardholder holding it there are four more stages — generation, embossing, personalisation and despatch — and none of them is an operation you call. Embossing in particular runs as a batch: requests accumulate through the day and go to the production bureau in one session, which is why the only published calls around it read the pending list and cancel from it. Delivery is the stage that does come back: the courier file, the movements and the barcode are all callable.

  3. Load funds

    Load from your payment leg with a funding reference; anonymous limit profile enforces the caps.

    newBalanceconfirmed

    Prepaid balance is not exposedLoading funds, card-to-card transfer and wallet balance have no operation in this platform's APIs. The programme can be issued and registered here; the money movement behind it comes from elsewhere.

  4. Register after KYC

    Attach the card to a customer once KYC completes — limits lift automatically.

    limitProfileREGISTERED

  5. Move money

    Card-to-card transfers inside the program and balance reads for wallet screens.

    availableBalancefor wallet UI

    Prepaid balance is not exposedLoading funds, card-to-card transfer and wallet balance have no operation in this platform's APIs. The programme can be issued and registered here; the money movement behind it comes from elsewhere.