Skip to main content

Create a payment instrument

post/paymentInstruments

Creates a payment instrument to issue a physical card, a virtual card, or a business account to your user.

For more information, refer to Issue cards or Issue business accounts.

Endpoint destination URL
https://balanceplatform-api-test.adyen.com/bcl/v1/paymentInstruments
Click to copy
balanceAccountIdstringRequired

The unique identifier of the balance account associated with the payment instrument.

cardobject

Contains information about the card. Required when you create a payment instrument of type card.

descriptionstring
Max length: 300

Your description for the payment instrument, maximum 300 characters.

issuingCountryCodestringRequired

The two-character ISO 3166-1 alpha-2 country code where the payment instrument is issued. For example, NL or US.

paymentInstrumentGroupIdstring

The unique identifier of the payment instrument group to which the payment instrument belongs.

referencestring
Max length: 150

Your reference for the payment instrument, maximum 150 characters.

statusstring

The status of the payment instrument. If a status is not specified when creating a payment instrument, it is set to Active by default. However, there can be exceptions for cards based on the card.formFactor and the issuingCountryCode. For example, when issuing physical cards in the US, the default status is Requested.

Possible values:

  • Active: The payment instrument is active and can be used to make payments.

  • Requested: The payment instrument has been requested. This state is applicable for physical cards.

  • Inactive: The payment instrument is inactive and cannot be used to make payments.

  • Suspended: The payment instrument is temporarily suspended and cannot be used to make payments.

  • Closed: The payment instrument is permanently closed. This action cannot be undone.

  • Stolen

  • Lost

typestringRequired

Type of payment instrument.

Possible value: card, bankAccount.

After submitting a call, you receive a response message to inform you that your request was received and processed.

Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.

HTTP Responses

  • 200 - OK

    The request has succeeded.

  • 400 - Bad Request

    A problem reading or understanding the request.

  • 401 - Unauthorized

    Authentication required.

  • 403 - Forbidden

    Insufficient permissions to process the request.

  • 422 - Unprocessable Entity

    A request validation error.

  • 500 - Internal Server Error

    The server could not process the request.