System-managed cards

Update a system card

Update the details of the system managed card identified by the id path parameter.

patch/managed_cards/system/{id}

Request

  • Base URL: https://sandbox.weavr.io/multi
  • URL: https://sandbox.weavr.io/multi/managed_cards/system/{id}
  • Auth: HTTP bearer and API key in header api-key

Path parameters

idstring required
Example:123456789

The unique identifier of a system managed card.

Headers

idempotency-refstring
Example:transfer-2026-08-07-001

A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.

Request body

tagstring

The tag field is a custom field that can be used to search and filter.

nameOnCardstring

The card holder's name for the card. This may be verified by merchants when the card is used online.

authForwardingDefaultTimeoutDecision'APPROVE' | 'DECLINE'

Default decision for auth forwarding on timeout

Example request

{
  "tag": "customer-123",
  "billingAddress": {
    "addressLine1": "1 High Street",
    "addressLine2": "Flat 2",
    "city": "London",
    "postCode": "W1A 1AA",
    "state": "Greater London",
    "country": "GB"
  },
  "externalData": [
    {
      "name": "Alex Smith",
      "value": "INV-1042"
    }
  ]
}

Response

Success

idstring required

The unique identifier of the card.

profileIdstring required

The profile Id which a specific identity, instrument, or transaction type is linked to.

Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.

You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.

Profile Ids can be found in the Multi Portal, in the API Credentials page.

externalHandlestring required

A uniquely generated code used to identify a card.

This code is to be used instead of the sensitive card number in order to refer to a card when opening a support ticket.

tagstring

The tag field is a custom field that can be used to search and filter.

currencystring required

The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

type'VIRTUAL' | 'PHYSICAL' required

The type of card:

  • VIRTUAL: Not a printed or embedded card. The card can be used online or added to digital wallets.
  • PHYSICAL: A physical card that can be printed and shipped to your customers or embedded in a Wearable device. It can be used at physical terminals.
cardBrand'MASTERCARD' | 'VISA' required

The card scheme, or brand of the card.

cardNumberFirstSixstring required

The first six digits of the card number.

cardNumberLastFourstring required

The last four digits of the card number.

nameOnCardstring required

The card holder's name for the card. This may be verified by merchants when the card is used online.

startMmyystring required

The start date of this card, in MMYY format.

expiryMmyystring required

The end date of this card, in MMYY format.

cardLevelClassification'CONSUMER' | 'CORPORATE' required

The card classification determines whether the card is from Consumer or Corporate BINs.

expiryPeriodMonthsinteger required

The validity timeframe of the card, in months.

renewalType'RENEW' | 'NO_RENEW' required

Indicates how the card will be handled once it is close to expiring.

  • RENEW: The card will be automatically renewed, keeping the same card number but with a new expiry date and CVV.
  • NO_RENEW: Once the expiry date is reached, the card is destroyed.
renewalTimestampinteger

The timestamp when the card will be renewed, expressed in Epoch timestamp using millisecond precision.

creationTimestampinteger required

The timestamp when the card was created, expressed in Epoch timestamp using millisecond precision.

authForwardingDefaultTimeoutDecision'APPROVE' | 'DECLINE'

Default decision for auth forwarding on timeout

modestring required

The mode with which this card was created:

  • A prepaid mode card has its own balance and can have funds transferred to or from it.
  • A debit mode card does not have its own balance but will be able to spend funds belonging to its parent managed account, subject to a configurable spend limit.
spendActor'SYSTEM' | 'USER'

Indicates whether the card is operated by a system or a user.

Example response

{
  "id": "234567890",
  "profileId": "10001",
  "externalHandle": "7F3E2B1A9C",
  "tag": "customer-123",
  "currency": "GBP",
  "cardNumber": {
    "value": "4532015112830366"
  },
  "cvv": {
    "value": "123"
  },
  "cardNumberFirstSix": "453201",
  "cardNumberLastFour": "0366",
  "nameOnCard": "Alex Smith",
  "startMmyy": "0826",
  "expiryMmyy": "0829",
  "expiryPeriodMonths": 36,
  "renewalTimestamp": 1880236800000,
  "creationTimestamp": 1786118400000,
  "billingAddress": {
    "addressLine1": "1 High Street",
    "addressLine2": "Flat 2",
    "city": "London",
    "postCode": "W1A 1AA",
    "state": "Greater London",
    "country": "GB"
  },
  "mode": "PREPAID_MODE",
  "externalData": [
    {
      "name": "Alex Smith",
      "value": "INV-1042"
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.