Set amount limit for 1 transaction

Set Amount Limit for 1 Transaction

This endpoint sets a maximum allowable amount for a single transaction on a specified payment card. It enforces a per-transaction spending cap, helping partners and their customers prevent unauthorized or excessive spending. The rule is applied directly to the card identified in the request.

Endpoint

POST /api/spendRules/amountLimit

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when you need to enforce a hard ceiling on individual transaction amounts for a payment card — for example, to support budgeting controls, restrict employee card spending, or add a fraud-prevention layer. This is especially useful when issuing virtual or physical cards to authorized users (subProfiles) and you want to cap each transaction at a defined value.

Request Body

{
  "paymentCardId": "card_a1b2c3d4e5f6",
  "value": 50000
}

Response

200 OK

A 200 Success response indicates the amount limit spend rule was successfully created and applied to the specified payment card. The response body is empty on success.

{}

Error Codes

Common Mistakes

• Omitting paymentCardId — this field is required and must be a non-empty string; the request will fail with a 400 error without it.
• Passing value as a decimal or float — the value field is an integer (int32); submit amounts in the smallest currency unit (cents) as a whole number (e.g., 50000 for $500.00).
• Applying the rule to a card that belongs to a personal customer subProfile that does not have spend rule permissions — verify the card's access level before setting rules.
• Using an expired or missing Bearer token — tokens expire after 10 minutes; refresh via POST /api/auth/refresh before making the call.

Related Endpoints

• POST /api/spendRules/velocityLimit — Set a maximum number of transactions allowed within a time period for a payment card
• POST /api/spendRules/merchantCategory — Restrict card spending to specific merchant category codes (MCCs)
• GET /api/spendRules/{paymentCardId} — Retrieve all spend rules currently applied to a payment card
• DELETE /api/spendRules/{spendRuleId} — Remove an existing spend rule from a payment card

Example

curl -X POST https://api.banking.netevia.dev/api/spendRules/amountLimit \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentCardId": "card_a1b2c3d4e5f6",
    "value": 50000
  }'