Detach Monthly Limit for Card
The POST /api/spendRules/detachVelocity endpoint removes the monthly spending limit, also known as a velocity rule, from a specified payment card. By sending a request with the card's unique identifier, this method detaches any previously configured monthly cap, enabling the card for unrestricted spending within that period. An optional spend rule ID can be provided to target a specific rule if multiple rules are in use.
Endpoint
POST /api/spendRules/detachVelocity
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 or administrator needs to remove a previously applied monthly spending cap from a payment card, granting unrestricted spending for that monthly period. This is appropriate for high-spend scenarios, special purchase events, or when business requirements no longer call for a hard monthly limit on a specific card. Always ensure proper authorization before modifying spend rules to maintain financial controls over the account.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| paymentCardId | string | Yes | The unique identifier of the payment card from which the monthly spending limit (velocity rule) will be removed. Minimum length: 1. |
| spendRuleId | string | No | The unique identifier of a specific spend rule to detach. If omitted, all velocity (monthly spending) rules are removed from the card. |
{
"paymentCardId": "card_a1b2c3d4e5f6",
"spendRuleId": "rule_x9y8z7w6v5u4"
}Response
200 OK
A 200 Success response confirms that the velocity rule (monthly spending limit) has been successfully detached from the specified payment card. No response body fields are returned.
{}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields (e.g., paymentCardId not provided) or validation error |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions to modify spend rules for the specified card |
| 404 | Payment card or spend rule not found |
| 500 | Internal server error |
Common Mistakes
- Omitting
paymentCardId— this field is required and must have at least one character; the request will fail with a 400 error if it is absent or empty. - Providing an invalid or mismatched
spendRuleId— ensure the spend rule ID belongs to the specified card to avoid a 404 or unexpected behavior. - Using an expired Bearer token — tokens are valid for 10 minutes; refresh before making the request if the token may have lapsed.
- Attempting to detach a velocity rule from a card that has no monthly limit set — verify the card's current spend rules before calling this endpoint.
Related Endpoints
POST /api/spendRules/attachVelocity— Attach a monthly spending limit (velocity rule) to a payment cardGET /api/spendRules— Retrieve all spend rules associated with a card or accountPOST /api/spendRules/detachSpendRules— Detach other types of spend rules from a payment card
Example
curl -X POST https://api.banking.netevia.dev/api/spendRules/detachVelocity \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"paymentCardId": "card_a1b2c3d4e5f6",
"spendRuleId": "rule_x9y8z7w6v5u4"
}' 200Success
