Returns a paginated list of the payment instruments associated with a balance account.
To fetch multiple pages, use the query parameters.For example, to limit the page to 3 payment instruments and to skip the first 6, use /balanceAccounts/{id}/paymentInstruments?limit=3&offset=6
.
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.
The request has succeeded.
Show more Show lessList of payment instruments associated with the balance account.
The unique identifier of the balance account associated with the payment instrument.
Contains the business account details. Returned when you create a payment instrument with type
bankAccount.
Contains information about the card payment instrument. Returned when you create a payment instrument with type
card.
Contains the card user's password and mobile phone number. This is required when you issue cards that can be used to make online payments within the EEA and the UK, or can be added to digital wallets. Refer to 3D Secure and digital wallets for more information.
The password used for 3D Secure password-based authentication. The value must be between 1 to 30 characters and must only contain the following supported characters.
Characters between a-z, A-Z, and 0-9
Special characters: äöüßÄÖÜ+-*/ç%()=?!~#'",;:$&à ùòâôûáúó
The phone number where the one-time password (OTP) is sent.
This object must have:
A type
set to mobile.
A number
with a valid country code.
A number
with more than 4 digits, excluding the country code.
Make sure to verify that the card user owns the phone number.
The brand variant of the physical or the virtual card.
Contact your Adyen Implementation Manager to get the values that are relevant to your integration. Examples: visadebit, mcprepaid.
Settings required when creating a physical or a virtual card.
Reach out to your Adyen contact to get the values that you can send in this object.
Overrides the activation label design ID defined in the configurationProfileId
. The activation label is attached to the card and contains the activation instructions.
Your app's URL, if you want to activate cards through your app. For example, my-app://ref1236a7d. A QR code is created based on this URL, and is included in the carrier. Before you use this field, reach out to your Adyen contact to set up the QR code process.
Maximum length: 255 characters.
Overrides the shipment bulk address defined in the configurationProfileId
.
The postal code.
Maximum length:
5 digits for addresses in the US.
10 characters for all other countries.
The two-letter ISO 3166-2 state or province code.
Maximum length: 2 characters for addresses in the US.
The ID of the card image. This is the image that will be printed on the full front of the card.
Overrides the carrier design ID defined in the configurationProfileId
. The carrier is the letter or packaging to which the card is attached.
The ID of the carrier image. This is the image that will printed on the letter to which the card is attached.
The ID of the card configuration profile that contains the settings of the card. For example, the envelope and PIN mailer designs or the logistics company handling the shipment. All the settings in the profile are applied to the card, unless you provide other fields to override them.
For example, send the shipmentMethod
to override the logistics company defined in the card configuration profile.
The three-letter ISO-4217 currency code of the card. For example, EUR.
Overrides the insert design ID defined in the configurationProfileId
. An insert is any additional material, such as marketing materials, that are shipped together with the card.
The two-letter ISO-639-1 language code of the card. For example, en.
The ID of the logo image. This is the image that will be printed on the partial front of the card, such as a logo on the upper right corner.
Overrides the PIN mailer design ID defined in the configurationProfileId
. The PIN mailer is the letter on which the PIN is printed.
The CVC2 value of the card.
The CVC2 is not sent by default. This is only returned in the
POST
response for single-use virtual cards.
The delivery contact (name and address) for physical card delivery.
The address of the contact.
The two-character ISO-3166-1 alpha-2 country code. For example, US.
If you don't know the country or are not collecting the country from the shopper, provide
country
asZZ
.
The postal code. Maximum length:
The full phone number of the contact provided as a single string. It will be handled as a landline phone. Examples: "0031 6 11 22 33 44", "+316/1122-3344", "(0031) 611223344"
The name of the contact.
The phone number of the contact.
The two-character ISO-3166-1 alpha-2 country code of the phone number. For example, US or NL.
The phone number. The inclusion of the phone number country code is not necessary.
The expiration date of the card.
Your description for the payment instrument, maximum 300 characters.
The two-character ISO 3166-1 alpha-2 country code where the payment instrument is issued. For example, NL or US.
The unique identifier of the payment instrument group to which the payment instrument belongs.
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 inactive.
Possible values:
active: The payment instrument is active and can be used to make payments.
inactive: The payment instrument is inactive and cannot be used to make payments.
suspended: The payment instrument is suspended, either because it was stolen or lost.
closed: The payment instrument is permanently closed. This action cannot be undone.
The reason for the status of the payment instrument.
Possible values: accountClosure, damaged, endOfLife, expired, lost, stolen, suspectedFraud, transactionRule, other.
If the reason is other, you must also send the statusComment
parameter describing the status change.