Version: 1.9

Card as a Service

Supply and securely push digital credit cards to a user's mobile wallet.
large hero image


The Card as a Service (CaaS) API allows you to integrate a collection of APIs into your user experience to supply a digital corporate credit card for business purchases and expenses. Using tokenization and encryption, the card can be pushed to the user's mobile wallet in a frictionless way. Extensive controls enhance the card's security, making fraud or misuse nearly impossible.


  • Extend corporate credit digitally and securely in real time.
  • Push cards to mobile wallets for use with Apple Pay® and Google Pay using encryption and tokenization.
  • Build tailored user experiences within your own ecosystem through custom API selections.
  • Set precise card amounts.
  • Deactivate cards in real time.
  • Implement Merchant Category Code (MCC) blocking and velocity controls.
  • Streamline the extension of corporate credit.
  • Attach receipt images to cards and authorizations.


Card-as-a-Service - workflow

Example use cases

Reconcile instant transactions.

A passenger is traveling on a major airline that is experiencing delays, causing the passenger to miss the last connecting flight back home. The airline issues funds to the passenger from their mobile app for a hotel stay overnight before offering a new flight in the morning. The passenger can push the funds from the mobile app to their device's mobile wallet and pay for a hotel stay and other incidentals for the evening. The card has controls imbedded that ensure the passenger only uses the card for its intended purposes. Once the passenger checks in for the flight the next morning, any remaining funds on the card will expire, allowing the airline to recoup any unspent funds.

Push cards for individual transactions.

An office support professional works for an online order fulfillment company that has struggled to fulfill multiple orders in a day due to manual payment and documentation processes. With the company's new implementation of the CaaS API, an individual digital card is issued for each order as it is created. The customers can push these cards to their mobile wallets for secure and easy checkout and payment processing. The company's app also supports access to digital receipts for an improved digital customer experience. By using an individual card for each order, it's easy to reconcile all the transactions for an order to the customer and the card.


  • Integration requires a U.S. Bank corporate card program for Corporate Travel, One Card or Purchasing Card.
  • If using Apple Pay or Google Pay:
    • An endorsement is required from U.S. Bank to achieve entitlement to push to mobile wallet.
    • Developer is required to have an Apple and Google developer account.


  • Corporate virtual cards can't be used for payroll, rewards or gifts.
  • Restrictions and/or addendums are required if using internationally.