Legacy Card Issuance Main Page

Please Integrate with our Native Card Issuance

Please integrate with our Native Card Issuance which we directly process and allows for further functionality and reliability.

The content of this page refers to our old card issuance which was built on top of a legacy processor that lead to occasional reliability issues. Because of this reason we consider our legacy card issuance as still in Open Beta.

Introduction

We have the capacity to issue cards on top of our accounts. They follow the functionality of those issued by traditional bank (e.g. ATM access, consumer protection), and give access to the interchange rails thus giving the ability to, for example, push funds to the card/account.

Cards can be issued on top of our deposit (,,), FBO (SUBACCOUNT-US), and () nodes. They can be virtual or physical and for businesses or individuals. Currently, we have the capacity to issue debit BINs (cards that are used in the card networks "debit card" payment network) and promptly credit BINs. A credit card functionality can still be created today with a debit BIN.

Node Type: Issued cards are a subnet of a node--they sit on top of an account or loan.

Recommended Steps to Issue a Card

  1. Make sure your controls (what you are allowed to do in our system) allow for card issuance.

  2. Have a successfully created node that allows for the creation of card subnets. See Accounts or Lending for more information on how to do so.

  3. Make sure the user for whom the card is going to be issued for has SEND-AND-RECEIVE permissions and that it's not a match in one of our sanctions lists click here for our guide on how to check for this.

  4. Submit our Create Debit Card call to create an inactive card. Please note the card (subnet) will have a status of PENDING while our system attempts to provision a card. If this is successful, the status will be updated to INACTIVE.

  5. User our Update Preferences API call to set the limits for POS withdrawals (pos_withdrawal_limit) and ATM withdrawals (atm_withdrawal_limit), as well as specify if foreign transactions are allowed (allow_foreign_transactions) depending on what is best for your use case.

  6. If you're shipping physical cards use our Ship Debit Card call to ship a physical card. We will send it to the address of the user we have on her base doc (learn more about base docs here. You can also expedite the shipment process, additional fees will apply.

  7. If you're shipping physical cards wait for confirmation by the user before activating the card. Example, have an Activate Card button in your app/website.

  8. Activate the Card.

Required KYC

In our system, cards sit on top of nodes. We capture user KYC at the node level, meaning that the KYC has been previously captured and not directly captured at the card level. Please keep in mind that KYC requirements may vary depending on the specific use case.

Physical Card Art

Our physical cards are white-labeled and can be customized by the platform (although they must be approved by the card network). To learn more about the physical art process please contact your Platform Architect or [email protected]

ATM Access

We currently offer fee-less withdrawals from ATMs on the MoneyPass Network. For ATMs that are not supported by our network, fees will be determined by the ATM and passed to the user.

We are in the process of adding:

  • GreenDot Network ATMs for withdrawal and deposits.
  • Allpoint network ATMs for deposits.

You can use our Find ATM Locations.

Sub-Resources

Below you can find links to the various debit card actions APIs, as well as to other supplementary resources.

APIs Relating to Our Card Issuance Product

Return Codes & Statuses

Legal

Please refer to our General Legal page for more information.
If you are looking for our external card processing product please refer here


Legacy Card Issuance Main Page


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.