Digital Card Issuance API - In Beta

Proposed Workflow for Building a New Card on the Omaha Platform for In-House Credit/ Debit

APIs Included

The New PAN is created by CORE and provided to the MB/OLB server.

CO-OP Endpoint

1. /omaha/new-account - Required
2. /omaha/external-status - Required
3. /omaha/auth-plus-strategy - Required
4. /omaha/reset-travel-strategy - Required
5. /omaha/card-activation - Required
6. /omaha/memo - Optional
7. /key-wrap.get - Required
8. /omaha/dci-cvv.get - Required
9. /omaha/pin-offset - Optional

Proposed Sample Steps

1. The New PAN is generated by CORE and sent via new-account endpoint to the Omaha platform for New Account Creation. (New Account and non-Mon files synch with Omaha.)
2. Request to remove “A” block on account: This is a required step as New Accounts are normally built with an “A” block.
3. Authorizations for Debit Cards Process to determine who performs the auth, limits, stand in, and the location of where to send messages. Similar to PCF for Debit Cards performed on the NEW ACCOUNT. (Debit and IHC)
4. Place card in FI “Home” Strategy: This is a required step by the Fraud team for added protection for the card's digital usage while the plastic card is being shipped.
5. DEACTIVATE the account for DCI: This is a Required Step to set the Activation Flag to Not Activated since All New Card Accounts are created Activated.
6. Optional - Memo for Audit.
7. The Encryption key needs to be sent by the client in order to receive securely wrapped key credentials.
8. DCI API Request: Obtain and return CVV and Expiration Date. Add Memo for the Card Management System.
9. Optional - PIN Change.

The Cardholder receives the plastic card ordered in step #1 by mail.