Spending controls let you restrict how much a cardholder can spend per transaction and which merchant categories they can transact with. These controls are optional and can be set at card creation or updated later.Documentation Index
Fetch the complete documentation index at: https://developers-sandbox.uqpaytech.com/llms.txt
Use this file to discover all available pages before exploring further.
Per-transaction limits
Set a maximum amount for each individual transaction. The limit must be greater than 0 and cannot exceed the system-defined maximum authorization threshold.Set at card creation
Includespending_controls in the Create Card request:
Update on an existing card
Use the Update Card endpoint:card.update.succeeded webhook fires.
Only the
PER_TRANSACTION interval is currently supported. The currency matches the card’s card_currency. When omitted during card creation, the system defaults to the account-level maximum per-transaction authorization limit.MCC controls
Merchant Category Code (MCC) controls restrict which types of merchants a card can transact with. You can define either an allowlist or a blocklist, but not both.Allowlist (allowed_mcc)
Only transactions with MCCs in this list are accepted. All other MCCs are declined.
Blocklist (blocked_mcc)
Transactions with MCCs in this list are declined. All other MCCs are accepted.
Set MCC controls
Includerisk_controls at card creation or use the Update Card endpoint:
Declined transaction example
When a transaction is declined due to MCC controls, the authorization webhook showstransaction_status: DECLINED with a description indicating the reason:
Related
- Create Card API
- Update Card API
- Card Updated webhook
- Supported BINs for risk control configurations — Which BINs support MCC controls

