Effective spend management is critical for minimizing risk and enforcing financial policies. The Unified Card API provides a structured framework for controlling how funds are accessed, ensuring you have granular oversight over every transaction.

How it Works

Spend limits in Passport operate on a "Inheritance and Override" model. It is important to understand the two levels of control:

Level 1: Program Limits Defined at the Card Program level during your initial setup with the Account Management team. These represent the absolute maximum velocity (e.g., "Max $10,000 per day") allowed for any card under that program. No individual card can exceed these global safety caps.
Level 2: Card/Customer Limits (Granular Control) Within the boundaries of the Program Limits, you can define specific restrictions for individual cards or users. While your Program allows up to $10,000/day, you may want to restrict a specific user’s card to only $500/day or limit a contractor's prepaid card to a $2,000 lifetime spend.

Type of Spend Limits

We support distinct categories of limits to give you precise control over cash flow:

Velocity Limits: Controls the total amount that can be spent within a rolling window.
- Daily Limit: The max spend allowed in a 24-hour period.
- Monthly Limit: The max spend allowed in a rolling 30-day window.
Transaction Limits (Per-Purchase): Controls the minimum and maximum amount for a single authorization.
Channel Limits: Separate controls for different purchase methods. You can set a high limit for POS (Point of Sale) usage while setting a strict, lower limit for ATM Withdrawals to minimize cash leakage.

Managing Limits

Managing limits allows you to enforce precise spend limits by dynamically setting transaction caps, frequency checks, and geographical restrictions at both the individual card and customer levels.

Card Spend Limits

These APIs allow retrieving/updating spend limits for a specific Card associated with the customer. This capability is fully supported for both Debit and Prepaid cards.

Using the GET /v1/customer/id/{id}/issuance/card/id/{id}/limit you can first view the card spend limits set for your card. Here the customer.id will be the ID of the customer and the card.id will be ID of the card you wish to view card limits for.
You can then dynamically update the spending limits using the POST /v1/customer/id/{id}/issuance/card/id/{id}/limit directly at the individual card level. You can update the following:

Node	Description
`limit.frequency`	The time interval at which the transaction limit applies, currently supporting `DAILY`.
`limit.transactionType`	The specific category of transaction the daily limit applies to, with possible values including `RETAIL`, `ATM`, and `ONLINE`.
`limit.count`	An integer that restricts the total number of transactions that can be conducted daily.
`limit.amount`	A predefined decimal value that caps the total monetary amount of transactions allowed daily.
`limit.location`	Indicates the geographical boundaries for card usage, such as restricting transactions to `DOMESTIC` only.

Customer Spend Limits

While individual cards can be restricted, you also have the ability to enforce limits at the Customer level.

Note that Customer Spend Limits are exclusively available for Prepaid Cards.

To view the customer's available corporate allowance, you can use the GET /v1/customer/id/{id}/issuance/cardProgram/id/{id}/limit endpoint using the Retrieve Customer Spend Limit API.
Using the POST v1/customer/id/{id}/issuance/cardProgram/id/{id}/limit endpoint, you can update the spend limits for a specific card program associated with the customer. Similar to card-level controls, these limits can be configured or retrieved based on the transaction type (such as ATM, ONLINE, or RETAIL) and their specific frequency (DAILY).