PATCH
/
v1
/
customers
/
{customerId}
/
accounts
/
{accountId}
/
cards
/
{cardId}
/
limits
curl --request PATCH \
  --url https://api.next.orenda.finance/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/limits \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "limitGroupId": "lg_123",
  "cardType": "VIRTUAL"
}
'
{
  "success": true,
  "message": "Card limit group updated successfully",
  "data": {
    "status": "success"
  }
}
{
  "success": false,
  "code": "VALIDATION_ERROR",
  "message": "newPin must be 4 digits"
}
{
  "success": false,
  "code": "UNAUTHORIZED",
  "message": "Unauthorized"
}
{
  "success": false,
  "code": "CARD_NOT_FOUND",
  "message": "Card not found"
}
{
  "success": false,
  "code": "INVALID_CARD_STATE",
  "message": "Card is already active"
}

Authorizations

​
Authorization
string
header
required

The user's access token. The program and environment come from the token.

Path Parameters

​
customerId
string
required

The customer's id.

​
accountId
string
required

The account the card belongs to. A customer can have several accounts; cards are issued against one.

​
cardId
string
required

The card id from create / get cards.

Body

application/json
​
limitGroupId
string

Move the card to this existing limit group. Send with cardType.

​
cardType
enum<string>

The card format, sent with limitGroupId.

Available options:
VIRTUAL,
PHYSICAL
​
limit
string

Set a limit amount directly. Send with type.

Example:

"1000.00"

​
type
enum<string>

The limit period, sent with limit.

Available options:
DAY,
WEEK,
MONTH,
YEAR,
LIFETIME

Response

Limits updated

​
success
boolean
Example:

true

​
message
string
Example:

"Card limit group updated successfully"

​
data
object