API Flows

This document highlights the Berkeley APIs that are called for basic use cases.

  • 1 Creating Cardholders and Activating Physical Cards
  • 2 Creating Cardholders and Activating Virtual Card
  • 3 Creating Cardholders for CIP/KYC Verifications
  • 4 Activating Card and Adding Funds to Card (Value Load)
  • 5 Pushing Funds
  • 6 Pulling Funds
  • 7 Retrieve and Set Pin
  • 8 Card Statuses
  • 9 Transfer to External Account
  • 10 Card to Card Transfer

Creating Cardholders and Activating Physical Cards

915

The create cardholder endpoint creates a cardholder and a card for the cardholder. Before being able to use a physical card, the card details found in the Get Cardholder Details endpoint must be used to activate the card, via the Activate Card endpoint.

Creating Cardholders and Activating Virtual Card

823

The Create cardholder endpoint creates a cardholder and a card for the cardholder. To activate a virtual card, the card details found in the Get Cardholder Details endpoint must be used in the modify account status endpoint to mark a card as active.

Creating Cardholders for CIP/KYC Verifications

1135

The create cardholder endpoint supports CIP/KYC verifications. SSN/SIN numbers may need to be provided for Berkeley to run a KYC verification based on the demographic data provided. The process above describes the Berkeley KYC workflow after a new cardholder is created.

See Result Codes or Test Codes

Activating Card and Adding Funds to Card (Value Load)

1016

Activate the card associated with the account, depending on if it is a virtual or physical card. Once the card is active, it will be ready to accept funds from the Master Funding Account. The create value load call will allow the user to load funds to a cardholder account.

Pushing Funds

1230

Pulling Funds

918

Activate the card associated with the account, depending on if it is a virtual or physical card. Once the card is active and funds are loaded onto it, the Create pull transaction call will credit a Financial Account for a specified amount.

Retrieve and Set Pin

827

The retrieve pin endpoint allows the user to return a specific PIN for a card on an account. The SET PIN endpoint will set a new pin for a card on an account.

Card Statuses

525

After creating a cardholder and associated card, the modify account status endpoint can be used to activate, suspend, or mark cards as lost or stolen.

Transfer to External Account

520

After creating a cardholder and associated card, the create External transfer endpoint leverages DirectSend to create a P2P or Card to Bank transfer.

Card to Card Transfer

578

After creating a cardholder and associated card, the Create card to card transfer endpoint transfers funds from an account to a recipient account.

📘

Related pages:

Card Issuing API Quickstart Guide
Cardholder Creation Validation
EFT Payments