Overview
User management
- Users
- User regulatory status
- User e-money
User verification
- User data format
- KYC documents
- UBO declarations
Wallets
- User wallets
- Client wallets
Cards
- Card registrations
- Cards
- Metadata
- Card validations
Card pay-ins
- Direct card pay-ins
- Recurring card pay-ins
- Preauthorizations
- Deposit preauthorizations
- Web card pay-ins
Banking pay-ins
- Bank wires
- Virtual IBAN
- Direct debits
- Web direct debits
APM pay-ins
- Apple Pay
- Bancontact
- BLIK
- Giropay
- Google Pay
- iDEAL
- Klarna
- MB WAY
- Multibanco
- Payconiq
- PayPal
- Satispay
Transfers
- Transfers
Refunds
- Refunds
Disputes
- Disputes
- Dispute documents
- Repudiations
- Dispute settlement
Payouts
- Bank accounts
- Payouts
FX conversions
- Conversion rates
- Quotes
- Conversions
Transactions
- Transactions
Helpers
- API responses
- Country authorizations
- Webhooks
- Events
- Reports
Platform account
- Client
- Dashboard permissions
List Cards for a User
Query parameters
Whether the card is active or not.
Path parameters
The unique identifier of the user.
Responses
The list of the cards created by the platform.
The card object created by the platform.
Format: “MMYY”
The expiration date of the card.
The card number, partially obfuscated.
Returned values: CB_VISA_MASTERCARD
, AMEX
, MAESTRO
, BCMC
Default value: CB_VISA_MASTERCARD
The type of the card. If not supplied, the default value will be taken into account.
Allowed values: CB
, VISA
, MASTERCARD
, AMEX
, MAESTRO
, BCMC
, JCB
, DISCOVER
The provider of the card.
Format: ISO-3166-1 alpha-3 three-letter country code (e.g., “FRA”)
The country of the card (which is the same as the country of the issuer).
The unique 5-number code of the issuer.
Whether the card is active or not. Setting this parameter to false
is irreversible and should be done once the pay-in is successful.
Returned values: The three-letter ISO 4217 code (EUR, GBP, etc.) of a supported currency (depends on feature, contract, and activation settings).
The currency of the card.
Returned values: UNKNOWN
, VALID
, INVALID
Whether the card is valid or not.
UNKNOWN
– No payment or card validation has been processed, so the validity of the card remains unknown.VALID
– The first payment or card validation using the card was processed successfully within 24 hours of the initial card registration.INVALID
– The first payment or card validation using the card was attempted and failed, or the status of the corresponding card registration wasCREATED
for more than 24 hours.
Once a card is set toINVALID
, it cannot be set back toVALID
. A new card registration will be necessary to make a payment.
The unique identifier of the user the card belongs to.
The unique identifier of the Card object.
Custom data added to this object.
In the case of the Card object, the tag value is inherited from the Card Registration object and is not editable.
The date and time at which the object was created.
The unique representation of the card number. This string can be used to track the card behavior while keeping the card information confidential.
Was this page helpful?