Set Daily ATM Withdrawal Limit

Set Daily ATM Withdrawal Limit

The Set Daily ATM Withdrawal Limit endpoint allows partners to configure a daily cap on ATM cash withdrawals for a specific payment card. By setting this spend rule, you restrict how much cash can be dispensed from ATMs within a 24-hour period. This helps reduce exposure to fraud, unauthorized access, and uncontrolled cash usage.

Endpoint

POST /api/spendRules/atmDailyLimit

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 a cardholder wants to place a hard limit on daily ATM cash withdrawals — for example, to guard against large unauthorized withdrawals if a card is lost or stolen. It is also useful for business customers managing authorized users (subProfiles) who need controlled cash access. Call this endpoint again with an updated value to modify an existing limit.

Request Body

FieldTypeRequiredDescription
paymentCardIdstringYesUnique identifier of the payment card to apply the ATM daily withdrawal limit to.
valueinteger (int32)NoMaximum amount in cents that can be withdrawn from ATMs in a single day. Omit or set to 0 to remove the limit.
{
  "paymentCardId": "card_a1b2c3d4e5f6g7h8",
  "value": 50000
}

Response

200 OK

A successful response confirms the spend rule has been created or updated. The API returns a success status; no additional fields are included in the response body.

{}

Error Codes

CodeWhen it happens
400Missing required fields or validation error (e.g., paymentCardId not provided or blank)
401Token missing, expired, or invalid
403Insufficient permissions to modify spend rules for this card
404Payment card not found
500Internal server error

Common Mistakes

  • Omitting paymentCardId — this field is required; the request will fail with a 400 error if it is missing or empty.
  • Passing value as a decimal (e.g., 500.00) instead of an integer in cents (e.g., 50000) — the field expects an int32 and fractional values will cause a validation error.
  • Using a stale or expired Bearer token — tokens expire after 10 minutes; refresh via POST /api/auth/refresh before retrying.
  • Applying a limit to a card that has already been closed or deactivated — verify card status before setting spend rules.

Related Endpoints

  • POST /api/spendRules/dailyLimit — Set a daily spend limit across all transaction types for a card
  • POST /api/spendRules/merchantCategoryBlock — Block or allow specific merchant category codes (MCCs) for a card
  • GET /api/spendRules/{paymentCardId} — Retrieve all active spend rules for a given card

Example

curl -X POST https://api.banking.netevia.dev/api/spendRules/atmDailyLimit \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "paymentCardId": "card_a1b2c3d4e5f6g7h8",
    "value": 50000
  }'
Body Params
int32
string
required
length ≥ 1
Headers
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Response
200

Success

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here!