Limits & Preferences
Configure the customer-level controls that govern how a customer transacts and how their money is routed: velocity limits and default account preferences.
Beyond onboarding a customer and opening accounts, PCE lets you set controls that shape how that customer transacts and how their money moves. Two of these are configured once per customer and then applied automatically to everything they do.
This section groups both controls in one place:
One configuration per customerBoth velocity limits and preferences are stored against a single customer, addressed by
idorexternalId. Each is set with a POST and read back with a GET, and sending the request again replaces what's stored — so always send the full set you want in effect.
What's in this section
Cap the number and cumulative amount of transactions a customer can process, separately for credit and debit, and optionally per payment method. Use this for risk management and transaction control.
Name the default Passport and external accounts a customer uses to settle exceptions, recover funds, process refunds, receive cash settlement, and run target-balance sweeps.
When to use which
| You want to… | Use |
|---|---|
| Limit how much or how often a customer can transact (overall or per rail) | Velocity Limits |
| Decide which account is debited or credited to settle a customer's exceptions, refunds, recovery, or cash settlement | Customer Preferences |
See also
- Accounts: the customer and Passport accounts these controls apply to
- Exceptions & reconciliation: the inbound items that preferences help settle
- Getting Started: authentication,
PromiseMode, webhooks, and shared setup
Updated 4 days ago