Skip to main content
Spending limits cap what a buyer’s card can spend. A transaction must fit every limit on its card, and limits work alongside the buyer’s approval, never instead of it. A card doesn’t need limits to pay. You need: your platform key, with the buyer’s ID in the sapiom-tenant header. Buyer keys can’t change limits, so your agent can’t raise one to get past a denial.

Limit types

Each card has three optional limits. Amounts are decimal strings, such as "100.00", and currency is USD.

Read a card’s limits

Returns the three limits, the saved version, and usage, which shows what the period and date-range limits have used and have remaining.

Set limits

Setting replaces all three limits. Send each one, with null for any you don’t want, and the version you read (0 the first time):
  • 409 with RULE_VERSION_CONFLICT means the limits changed since you read them. Read again, then set.
  • 409 with CARD_UNAVAILABLE means the card isn’t ready yet.
  • Changing a period or date-range limit starts a fresh allowance. Saving it unchanged keeps what has been used.
  • A merchant refund or cancellation doesn’t restore spending capacity.