> ## Documentation Index > Fetch the complete documentation index at: https://developers.portao3.com.br/llms.txt > Use this file to discover all available pages before exploring further. # List card transactions > Lists a card's transactions, newest first: purchases, their settlements and refunds, and the fees charged on the card. Narrow it to a period with `startDate` and `endDate` (both, or neither), to a merchant with `merchantName`, or to `DEBIT` / `CREDIT` / `NONE` transactions with `financialImpactType` (comma-separated for several), and page with `limit` + `next`. A purchase and its later settlement or refund are separate transactions, linked through `cardTransaction.linkedTransactions`. Use `default` as `walletId` for the organization's main wallet, and send `x-environment: LIVE` for a production card. Any member of the organization can list a card's transactions. ## OpenAPI ````yaml /api-reference/banking.openapi.json get /realms/{realmId}/organizations/{organizationId}/accounts/{accountId}/wallets/{walletId}/cards/{cardId}/transactions openapi: 3.0.3 info: title: Banking version: 1.0.0 description: >- Portão 3 banking API. Every endpoint requires a bearer token in the Authorization header (Authorization: Bearer ) unless its page states otherwise; see the Authentication guide. That requirement is not repeated per endpoint. Generated by tools/openapi from code (routes + security) and the hand-written spec (request/response bodies). Banking attaches a zod validationSchema at the route; request bodies are resolved from it (object + array roots). Responses have no presenter layer, so they stay tier=unknown. Confidence tiers: generated:typed=215 copied:manual=4 unknown=52. servers: - url: https://api.banking.v2.portao3.com.br/ description: production - url: https://api.banking.dev.3pers.com.br/ description: development security: [] tags: - name: Accounts - name: Account Limits - name: Wallets - name: Cards - name: Card Limits - name: Cards 3DS - name: PIX - name: PIX Keys (DICT) - name: PIX Charges - name: PIX Automatic - name: PIX Initiation (Open Finance) - name: PIX Infractions (MED) - name: Boleto - name: Boleto Charges - name: TED - name: Transfers - name: Transactions - name: Cashback - name: Currency Codes - name: Reversals paths: /realms/{realmId}/organizations/{organizationId}/accounts/{accountId}/wallets/{walletId}/cards/{cardId}/transactions: get: tags: - Cards summary: List card transactions description: >- Lists a card's transactions, newest first: purchases, their settlements and refunds, and the fees charged on the card. operationId: >- getRealmsByRealmIdOrganizationsByOrganizationIdAccountsByAccountIdWalletsByWalletIdCardsByCardIdTransactions parameters: - name: realmId in: path required: true description: |- ID of your realm. Format: `UUID` schema: type: string format: uuid example: f495ff0c-ab54-4f99-8e92-ca8682e4de9b - name: organizationId in: path required: true description: |- ID of the organization the card belongs to. Format: `UUID` schema: type: string format: uuid example: c4bd3f21-dfbd-44e8-8055-68ba15bed410 - name: accountId in: path required: true description: ID of the organization's account (24 hexadecimal characters). schema: type: string pattern: ^[0-9a-fA-F]{24}$ example: 66f2a1c7b4d3e80012c9a0b4 - name: walletId in: path required: true description: >- ID of the card's wallet (24 hexadecimal characters), or `default` for the organization's main wallet. schema: type: string pattern: ^([0-9a-fA-F]{24}|default)$ example: 66f2a3d1b4d3e80012c9a0d2 - name: cardId in: path required: true description: ID of the card (24 hexadecimal characters). schema: type: string pattern: ^[0-9a-fA-F]{24}$ example: 66f2a4b8b4d3e80012c9a0e1 - name: x-environment in: header required: false description: >- Environment of the card: `LIVE` (production) or `TEST` (sandbox). When you omit it, the request runs in `TEST`; any other value is rejected. schema: type: string enum: - LIVE - TEST example: LIVE - name: startDate in: query required: false description: >- Start of the period, inclusive: an ISO 8601 date-time (`2026-11-01T03:00:00.000Z`) or date (`2026-11-01`, read as midnight UTC). The period applies only when you send both `startDate` and `endDate`. schema: type: string example: '2026-11-01T03:00:00.000Z' - name: endDate in: query required: false description: End of the period, inclusive, in the same format as `startDate`. schema: type: string example: '2026-12-01T02:59:59.999Z' - name: merchantName in: query required: false description: >- Only transactions whose merchant name contains this text (case-insensitive). schema: type: string maxLength: 256 example: AIRLINES - name: financialImpactType in: query required: false description: >- Only transactions with these effects on the balance (case-insensitive): `DEBIT` (money out), `CREDIT` (money in) or `NONE` (no effect, such as a declined authorization). Other values match no transaction. --- Example (comma-separated list): `?financialImpactType=DEBIT,CREDIT` schema: type: array items: type: string maxLength: 64 style: form explode: false - name: next in: query required: false description: >- Cursor returned as `next` by the previous page. Omit it for the first page. schema: type: string example: NjZmMmE3ZTliNGQzZTgwMDEyYzlhMTEy - name: limit in: query required: false description: Page size. Defaults to 15. schema: type: integer minimum: 0 exclusiveMinimum: true example: 15 responses: '200': description: Successful response content: application/json: schema: type: object properties: items: type: array items: type: object properties: _id: type: string description: ID of the transaction. example: 66f2a7e9b4d3e80012c9a112 environment: type: string enum: - LIVE - TEST description: >- Environment of the transaction: `LIVE` (production) or `TEST` (sandbox). example: LIVE realmId: type: string description: ID of the realm. example: f495ff0c-ab54-4f99-8e92-ca8682e4de9b format: uuid organizationId: type: string description: ID of the organization. example: c4bd3f21-dfbd-44e8-8055-68ba15bed410 format: uuid accountId: type: string description: ID of the organization's account. example: 66f2a1c7b4d3e80012c9a0b4 walletId: type: string description: ID of the wallet the card spends from. example: 66f2a3d1b4d3e80012c9a0d2 cardId: type: string description: ID of the card. example: 66f2a4b8b4d3e80012c9a0e1 balanceCategory: type: string description: >- Balance category of the wallet the amount was taken from or returned to, such as `FLEX_NATIONAL`, `FLEX_INTERNATIONAL`, `ADS`, `TRAVEL` or `FOOD`. example: ADS availableBalanceBefore: type: number nullable: true description: >- Balance of that category before the transaction, in cents (BRL). Can be `null`. example: 1250000 financialImpactType: type: string enum: - DEBIT - CREDIT - NONE description: >- Effect on the balance: `DEBIT` (money out), `CREDIT` (money back in, such as a refund) or `NONE` (no effect, such as a declined authorization). example: DEBIT responseCode: type: number description: >- Result code of the authorization. `0` is approved; a few other codes are approvals too, such as `10` (partially approved) and `400` (approved offline) — most other codes are decline reasons, such as `5` (declined) or `51` (insufficient funds). Use `financialImpactType` to know whether money moved. Absent on a few older transactions. example: 0 msgType: type: number description: >- ISO 8583 message type, such as `1100` (authorization), `1120` (settlement or credit), `1400` (refund) or `1420` (reversal). example: 1100 txnType: type: number description: >- ISO 8583 transaction type, such as `0` (purchase), `1` (cash withdrawal), `14` (return) or `100` (settlement debit). Absent on a few older transactions. example: 0 effectiveAt: type: string description: >- When the transaction happened. Lists are ordered by it, newest first, and the period filters apply to it. example: '2026-11-02T15:20:31.000Z' format: date-time billingAmount: type: number description: Amount charged to the wallet, in cents (BRL). example: 18990 billingAmountAuthorized: type: number description: >- Amount authorized, in cents (BRL). Summaries and exports add this one up. example: 18990 billingCurrency: type: string description: >- Currency of the billed amounts, as an ISO 4217 numeric code: always `986` (Brazilian real). example: '986' cardTransaction: type: object properties: _id: type: string description: ID of the details record. example: 66f2a7e9b4d3e80012c9a115 acquiringCountryCode: type: string nullable: true description: >- Country of the merchant's acquirer, as an ISO 3166 numeric code. Can be `null`. example: '076' acquiringId: type: string nullable: true description: >- Identifier of the merchant's acquirer. Can be `null`. example: '012345' localTime: type: string description: Date and time of the purchase. example: '2026-11-02T15:20:31.000Z' format: date-time txnCurrency: type: string description: >- Currency of the purchase, as an ISO 4217 numeric code (`986` is the Brazilian real). example: '986' txnAmount: type: number description: >- Amount of the purchase, in cents of `txnCurrency`. example: 18990 txnAmountAuthorized: type: number description: Amount authorized, in cents of `txnCurrency`. example: 18990 linkedTransactions: type: array items: type: object properties: _id: type: string description: ID of the link. example: 66f2a7e9b4d3e80012c9a114 transactionId: type: string description: ID of the related transaction. example: 66f2a7e9b4d3e80012c9a113 linkType: type: string description: >- How the two are related, from this transaction's point of view. `CLEARING_CREDITS` / `CLEARING_CREDITED_BY` link a refund to the purchase it refunds; `CLEARING_DEBITS` / `CLEARING_DEBITED_BY` link a purchase to its settlement; `REVERSES` / `REVERSED_BY` and `EXPIRES` / `EXPIRED_BY` link an authorization to its reversal or expiry. Other values describe further processing steps. example: CLEARING_DEBITED_BY createdAt: type: string description: When the link was created. example: '2026-11-03T09:12:40.000Z' updatedAt: type: string description: When the link last changed. example: '2026-11-03T09:12:40.000Z' required: - _id - transactionId - linkType - createdAt - updatedAt description: >- A link between this transaction and a related one (its settlement, a refund, …). description: >- Related transactions: the settlement, a refund, a reversal. mcc: type: string nullable: true description: >- Merchant category code (MCC) of the merchant. Can be `null`. example: '5968' merchantCity: type: string nullable: true description: City of the merchant. Can be `null`. example: SAO PAULO merchantCountry: type: string nullable: true description: >- Country of the merchant, as an ISO 3166 alpha-3 code. Can be `null`. example: BRA merchantId: type: string nullable: true description: Identifier of the merchant. Can be `null`. example: '000000000473921' merchantName: type: string nullable: true description: Name of the merchant. Can be `null`. example: LOJA EXEMPLO expired: type: boolean description: >- Whether the authorization expired without being settled. Absent on older transactions. example: false cleared: type: boolean description: >- Whether the purchase has been settled. Absent on older transactions. example: true overcleared: type: boolean description: >- Whether it was settled for more than was authorized. Absent on older transactions. example: false reversed: type: boolean description: >- Whether the authorization was reversed. Absent on older transactions. example: false posEntryMode: type: string nullable: true description: >- How the card was used, such as `E-Commerce` or `Contactless`. Can be `null`. example: E-Commerce recurring: type: boolean nullable: true description: >- Whether the merchant flagged the purchase as recurring. Absent or `null` when unknown. example: false mobileWalletProvider: type: number description: >- Device wallet the card was used through: `103` (Apple Pay), `216` (Google Pay), `217` (Samsung Pay) or `327` (a card stored by a merchant). Absent when the card was used directly, and on transactions before August 2026. example: 103 required: - _id - localTime - txnCurrency - txnAmount - txnAmountAuthorized - linkedTransactions description: Details of a card purchase. Absent on a fee. feeTransaction: type: object properties: _id: type: string description: ID of the details record. example: 66f2a7e9b4d3e80012c9a117 linkedTransactions: type: array items: type: object properties: _id: type: string description: ID of the link. example: 66f2a7e9b4d3e80012c9a114 transactionId: type: string description: ID of the related transaction. example: 66f2a7e9b4d3e80012c9a113 linkType: type: string description: >- How the two are related, from this transaction's point of view. `CLEARING_CREDITS` / `CLEARING_CREDITED_BY` link a refund to the purchase it refunds; `CLEARING_DEBITS` / `CLEARING_DEBITED_BY` link a purchase to its settlement; `REVERSES` / `REVERSED_BY` and `EXPIRES` / `EXPIRED_BY` link an authorization to its reversal or expiry. Other values describe further processing steps. example: CLEARING_DEBITED_BY createdAt: type: string description: When the link was created. example: '2026-11-03T09:12:40.000Z' updatedAt: type: string description: When the link last changed. example: '2026-11-03T09:12:40.000Z' required: - _id - transactionId - linkType - createdAt - updatedAt description: >- A link between this transaction and a related one (its settlement, a refund, …). description: >- Related transactions, such as the purchase the fee was charged on. description: type: string description: Description of the fee. example: Tarifa de compra internacional txnCurrency: type: string description: >- Currency of the fee, as an ISO 4217 numeric code. example: '986' txnAmount: type: number description: Amount of the fee, in cents of `txnCurrency`. example: 664 txnAmountAuthorized: type: number description: Amount authorized, in cents of `txnCurrency`. example: 664 external: type: object properties: invoiceId: type: string description: ID of the invoice the fee belongs to. example: 66f2a8a1b4d3e80012c9a120 dealId: type: string description: ID of the deal the fee belongs to. example: 66f2a8a1b4d3e80012c9a121 contractId: type: string description: ID of the contract the fee belongs to. example: 66f2a8a1b4d3e80012c9a122 description: >- References of the fee to what it was charged for. creditParty: type: object properties: _id: type: string description: ID of the party record. example: 66f2a7e9b4d3e80012c9a118 type: type: string description: >- `LOCAL` (a wallet at Portão 3) or `REMOTE_PIX` (a PIX key elsewhere). example: LOCAL local: type: object properties: realmId: type: string description: ID of the wallet's realm. example: f495ff0c-ab54-4f99-8e92-ca8682e4de9b organizationId: type: string description: ID of the wallet's organization. example: c4bd3f21-dfbd-44e8-8055-68ba15bed410 accountId: type: string description: ID of the wallet's account. example: 66f2a1c7b4d3e80012c9a0b4 walletId: type: string description: ID of the wallet. example: 66f2a3d1b4d3e80012c9a0d2 description: The wallet, for a `LOCAL` party. remote: type: object properties: pixKey: type: string description: The PIX key. example: financeiro@acme.com.br pixDict: type: string description: >- Type of the PIX key, such as `EMAIL` or `CNPJ`. example: EMAIL description: The PIX key, for a `REMOTE_PIX` party. required: - type description: Where the fee goes. debitParty: type: object properties: _id: type: string description: ID of the party record. example: 66f2a7e9b4d3e80012c9a118 type: type: string description: >- `LOCAL` (a wallet at Portão 3) or `REMOTE_PIX` (a PIX key elsewhere). example: LOCAL local: type: object properties: realmId: type: string description: ID of the wallet's realm. example: f495ff0c-ab54-4f99-8e92-ca8682e4de9b organizationId: type: string description: ID of the wallet's organization. example: c4bd3f21-dfbd-44e8-8055-68ba15bed410 accountId: type: string description: ID of the wallet's account. example: 66f2a1c7b4d3e80012c9a0b4 walletId: type: string description: ID of the wallet. example: 66f2a3d1b4d3e80012c9a0d2 description: The wallet, for a `LOCAL` party. remote: type: object properties: pixKey: type: string description: The PIX key. example: financeiro@acme.com.br pixDict: type: string description: >- Type of the PIX key, such as `EMAIL` or `CNPJ`. example: EMAIL description: The PIX key, for a `REMOTE_PIX` party. required: - type description: Where the fee is paid from. required: - _id - linkedTransactions - txnCurrency - txnAmount - txnAmountAuthorized description: >- Details of a fee charged on the card. Present only on a fee. enrichment: type: object properties: _id: type: string description: ID of the record. example: 66f2a7e9b4d3e80012c9a116 merchant: type: string nullable: true description: >- Recognized merchant brand, such as `AMAZON` or `UBER`. `null` when none is recognized. example: GOOGLE category: type: string nullable: true description: >- Spending category of the purchase, such as `ADVERTISING_AND_MARKETING`, `AIRLINES_AND_TRAVEL`, `FOOD_AND_DINING` or `UNCATEGORIZED`. `null` when it couldn't be determined. example: ADVERTISING_AND_MARKETING rulesVersion: type: number description: >- Version of the recognition rules that produced this. example: 3 required: - _id - merchant - category - rulesVersion description: >- Merchant and spending category recognized for the purchase. Absent on older ones. customFields: type: object additionalProperties: {} description: >- Values of the organization's transaction custom fields, keyed by each field's `slug`. Absent when the transaction has none. --- Example: `{"cost-center":"CC-1020"}` example: cost-center: CC-1020 spendReview: type: object properties: status: type: string description: '`PENDING_APPROVAL`, `APPROVED` or `DECLINED`.' example: APPROVED policyId: type: string description: ID of the policy that governs the review. example: 6a01b2c3d4e5f60718293a4b policyRequestId: type: string description: ID of the approval request. example: 6a01b2c3d4e5f60718293a4c autoApproved: type: boolean description: >- Whether the policy approved it without an approver. example: false requester: type: object properties: userId: type: string description: ID of the user. example: e3553bc1-5e20-4e17-b22a-a796fda0aa99 name: type: string description: Name of the user. example: Mariana Costa email: type: string description: E-mail of the user. example: mariana.costa@acme.com.br required: - userId - name - email description: Who submitted the transaction for review. requestedAt: type: string description: When it was submitted. example: '2026-11-02T18:02:11.000Z' format: date-time approvalExpiresAt: type: string description: When a pending review expires. example: '2026-11-09T18:02:11.000Z' format: date-time decidedAt: type: string description: When it was decided. example: '2026-11-03T10:15:00.000Z' format: date-time declineOutcome: type: string description: >- Why a `DECLINED` review ended: `DENIED`, `CANCELED` or `EXPIRED`. example: DENIED decisionReason: type: string description: The approver's reason. example: Receipt missing required: - status - policyId - policyRequestId - requester - requestedAt description: >- The expense review, once the transaction was submitted for approval. spendReviewSubmissionLeaseUntil: type: string description: >- Until when a submission for review is being processed. example: '2026-11-02T18:03:11.000Z' format: date-time receipts: type: string description: Receipt attached to an older transaction. example: https://files.example.com/receipt.pdf description: type: string description: Legacy description kept on a few older transactions. example: Campaign ads timezoneOffset: type: number description: >- Legacy time-zone offset kept on a few older transactions. example: -3 external: type: object properties: transactionId: type: string description: >- Identifier of the transaction at the card issuer. example: 0F1E2D3C4B5A69788796A5B4C3D2E1F0 description: Identifier of the transaction at the card issuer. processingType: type: string enum: - INSTANT - DELAYED description: >- `INSTANT` (processed as it happened) or `DELAYED` (processed later). example: INSTANT internalErrorCode: type: string description: >- Code of an internal processing error, when there was one. example: INSUFFICIENT_FUNDS createdAt: type: string description: When the transaction record was created. example: '2026-11-02T15:20:33.000Z' format: date-time updatedAt: type: string description: When the transaction record last changed. example: '2026-11-03T09:12:40.000Z' format: date-time __v: type: number description: >- Version of the record, incremented by some updates. Absent on a few older ones. example: 0 required: - _id - environment - realmId - organizationId - accountId - walletId - cardId - availableBalanceBefore - financialImpactType - msgType - effectiveAt - billingAmount - billingAmountAuthorized - billingCurrency - external - processingType - createdAt - updatedAt description: >- A transaction of a card: a purchase, its settlement or refund, or a fee. description: The transactions of this page. next: type: string nullable: true description: >- Cursor of the next page: pass it as `next` to read it. `null` on the last page. example: NjZmMmE3ZTliNGQzZTgwMDEyYzlhMTEy required: - items - next description: A page of a card's transactions, newest first. '404': description: >- `ACCOUNT_NOT_FOUND` — No account with this ID exists in the organization. `WALLET_NOT_FOUND` — No wallet with this ID exists in the account and environment. `CARD_NOT_FOUND` — No card with this ID exists in the wallet and environment. content: application/json: schema: type: object properties: traceId: type: string description: >- Identifier of the request that failed. Quote it when contacting support. example: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: type: string enum: - ACCOUNT_NOT_FOUND - WALLET_NOT_FOUND - CARD_NOT_FOUND description: >- Stable, machine-readable error code. Branch on this, never on `message`. origin: type: string enum: - BANKING description: Service that produced the error. message: type: string description: >- Human-readable explanation. Its wording may change without notice. required: - traceId - code - origin - message example: traceId: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: ACCOUNT_NOT_FOUND origin: BANKING message: Account not found '422': description: >- `BAD_REQUEST` — A path or query parameter is invalid; `fields` lists each one. content: application/json: schema: type: object properties: traceId: type: string description: >- Identifier of the request that failed. Quote it when contacting support. example: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: type: string enum: - BAD_REQUEST description: >- Stable, machine-readable error code. Branch on this, never on `message`. origin: type: string enum: - BANKING description: Service that produced the error. message: type: string description: >- Human-readable explanation. Its wording may change without notice. fields: type: array description: >- One entry per invalid request field (validation errors only). items: type: object properties: field: type: string description: >- Path of the invalid field, e.g. `label` or `values[0].value`. example: label message: type: string description: Why the field was rejected. example: label is required code: type: string description: >- `_` — e.g. `LABEL_REQUIRED`, `TYPE_ONE_OF`, `VALUES_VALUE_TYPE_ERROR`. example: LABEL_REQUIRED values: type: array items: type: string description: >- The accepted values, when the field is an enumeration. required: - field - message - code required: - traceId - code - origin - message example: traceId: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: BAD_REQUEST origin: BANKING message: >- Bad Request: Your request is invalid or incomplete. Please make sure you are requesting with the right fields. fields: - field: merchantName message: 'Too big: expected string to have <=256 characters' code: MERCHANTNAME_MAX ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.