List cards
Cards are paginated. Passlimit and the next cursor from the previous response to page through results.
List the cards in a single wallet:
{ "items": [...], "next": "<cursor>" }. Each item carries the masked PAN, status, and your customFields. To read the full PAN and CVV of a specific card, call the details endpoint — see Issue virtual cards.
Reference: GET .../wallets/{walletId}/cards · GET .../accounts/{accountId}/cards
Block and unblock a card
Blocking a card sets itsstatus to BLOCKED and stops new authorizations without destroying the card. Unblocking restores it to ACTIVE.
POST .../cards/{cardId}/block · POST .../cards/{cardId}/unblock
Read a card’s transactions
List the transactions on a card within a date range. Results are paginated with the samenext cursor pattern.
Reference:
GET .../cards/{cardId}/transactions
Card webhooks
Instead of polling, subscribe to webhooks to react to card activity in real time. All Portão 3 webhooks share the same envelope — see Receive webhooks for the delivery model and how to deduplicate.A transaction happened on a card
CARD_TRANSACTION (source WALLET) fires when a card is charged; a refused authorization fires CARD_TRANSACTION_REFUSED. The payload mirrors a transaction item: cardId, billingAmount, balanceCategory, and the nested cardTransaction with the merchant details and mcc.
A card needs a verification code (tokenization)
When a cardholder adds the card to a device wallet (Apple Pay, Google Pay), the issuer sends an activation code you must relay to the cardholder:activationCode to the cardholder so they can finish validating the card in their device wallet.
Next steps
Receive webhooks
The notification envelope and the full event catalog.
Control card spending
Limits, rules, and available balance.