Create a spend control
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Details of the spend control to create
If set, create a case for transactions that do not conform to the spend control
If set, decline transactions that do not conform to the spend control
The direction of funds flow to which a spend control applies. To limit the rate of funds flowing out of an account, use DEBIT. To limit the rate of funds flowing in to an account, use CREDIT. If this is not set, the spend control applies to debits (ie spending) only.
CREDITS, DEBITS Indicates if spend control is active
true
Name assigned to spend control
The time range to which the spend control applies
Controls how spend is measured for enforcement:
ACCOUNT - Per-account: each account's spend is checked independently (default)CUSTOMER - Per-customer: spend is aggregated across all accounts owned by the customerCARDS - Per-card: spend is aggregated per specific cardACCOUNT, CARDS, CUSTOMER Monetary limit for the spend control in the smallest currency unit (eg cents). At least one of amount_limit and transaction_count_limit must be specified.
x >= 0Geographic restrictions for spend controls
The type of resource manager
BANK, FINTECH, PLATFORM merchant category codes for spend control
10specify a specific MCC or a range of MCCs using a dash (-)
^\d{4}(-\d{4})?$A list of payment sub-types to which a spend control will apply, if set. If not set or the array is empty, then the spend control will apply to all sub-types.
A list of payment types to which a spend control will apply, if set. If not set or the array is empty, then the spend control will apply to all types of payments.
The type of payment to which a spend control applies. If this is not set, the spend control applies to all spending, regardless of payment type.
ACH, CARD, CASH, CHECK, EFT_CA, EXTERNAL_CARD, INTERNAL_TRANSFER, SYNCTERA_PAY, WIRE The scope determines which accounts this spend control applies to:
ACCOUNT - Applies only to accounts explicitly linked via account mappings (default)CUSTOMER - Applies only to customers explicitly linked via customer mappingsCARDS - Applies only to cards explicitly linked via card mappingsFINTECH - Automatically applies to all accounts under the fintech tenantBANK - Automatically applies to all accounts under the bank tenantACCOUNT, BANK, CARDS, CUSTOMER, FINTECH Number of transactions allowed by the spend control, regardless of transaction amounts. At least one of amount_limit and transaction_count_limit must be specified.
x >= 0Spend control details
A count of how many accounts are using this spend control
x >= 0A count of how many cards are using this spend control
x >= 0A count of how many customers are using this spend control
x >= 0The id of the tenant containing the resource.
"abcdef_ghijkl"
If set, create a case for transactions that do not conform to the spend control
If set, decline transactions that do not conform to the spend control
The timestamp representing when the spend control was created
"2010-05-06T12:23:34.321Z"
The direction of funds flow to which a spend control applies. To limit the rate of funds flowing out of an account, use DEBIT. To limit the rate of funds flowing in to an account, use CREDIT. If this is not set, the spend control applies to debits (ie spending) only.
CREDITS, DEBITS Spend Control ID
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
Indicates if spend control is active
true
The timestamp representing when the spend control was last modified
"2010-05-06T12:23:34.321Z"
Name assigned to spend control
The time range to which the spend control applies
Controls how spend is measured for enforcement:
ACCOUNT - Per-account: each account's spend is checked independently (default)CUSTOMER - Per-customer: spend is aggregated across all accounts owned by the customerCARDS - Per-card: spend is aggregated per specific cardACCOUNT, CARDS, CUSTOMER Monetary limit for the spend control in the smallest currency unit (eg cents). At least one of amount_limit and transaction_count_limit must be specified.
x >= 0Geographic restrictions for spend controls
The type of resource manager
BANK, FINTECH, PLATFORM merchant category codes for spend control
10specify a specific MCC or a range of MCCs using a dash (-)
^\d{4}(-\d{4})?$A list of payment sub-types to which a spend control will apply, if set. If not set or the array is empty, then the spend control will apply to all sub-types.
A list of payment types to which a spend control will apply, if set. If not set or the array is empty, then the spend control will apply to all types of payments.
The type of payment to which a spend control applies. If this is not set, the spend control applies to all spending, regardless of payment type.
ACH, CARD, CASH, CHECK, EFT_CA, EXTERNAL_CARD, INTERNAL_TRANSFER, SYNCTERA_PAY, WIRE The scope determines which accounts this spend control applies to:
ACCOUNT - Applies only to accounts explicitly linked via account mappings (default)CUSTOMER - Applies only to customers explicitly linked via customer mappingsCARDS - Applies only to cards explicitly linked via card mappingsFINTECH - Automatically applies to all accounts under the fintech tenantBANK - Automatically applies to all accounts under the bank tenantACCOUNT, BANK, CARDS, CUSTOMER, FINTECH Number of transactions allowed by the spend control, regardless of transaction amounts. At least one of amount_limit and transaction_count_limit must be specified.
x >= 0