Capital One Canada icon

Capital One Canada Data API

Capital One Bank (Canada Branch) · Banking

Capital One Canada is the official Android app from Capital One Bank (Canada Branch) for credit-card customers in Canada. Cardholders sign in with a username and password or supported biometric credentials to check card balances, available credit, spending and payment history. They can manage linked chequing and Interac e-Transfer payment options, lock or unlock a card, set a PIN and activate a newly delivered card. The app also brings together miles and rewards redemption, purchase eraser, spending insights, Credit Keeper scores, credit-limit increase offers, statements and mobile alerts. English and French support and Quebec-specific customer preferences serve Canadian cardholders managing their everyday credit-card accounts.

Canadian card-account records connect accountReferenceId and lastFourCardNumber with currentBalance, creditLimit, availableCredit and statementBalance. Repayment planning adds minimumPayment and minimumPaymentDueDate, while accountStatus and cardLock describe the account and card-control state and the profile-level QuebecCustomer flag marks Quebec profiles. Posted purchases carry merchantName, transactionAmount, transactionDate and transactionPostedDate, giving personal-finance and collections teams a way to align balances with dated activity.

Saved funding sources use paymentAccountReferenceId, paymentAccountType, paymentAccountNickName and lastFourDdaNumber; payment records add paymentReferenceId, paymentAmount and postedDate for repayment matching. Rewards records pair rewardsCurrency with redemptionOptionsList, and track redemptionAmount, redemptionCategoryCode, redemptionCurrencyCode, redemptionOrderStatus and redemptionDate. Purchase-eraser records link eligibility to creditCardTransactionId, supporting loyalty reconciliation alongside card-payment operations.

Credit Keeper adds creditScoreValue and creditScoreLevel; line-increase records include clipOfferAmount, scoreEventDate, offerId and, after acceptance, fulfillmentReferenceId. Statement records carry documentId, documentType and documentDate, while includeStatements and hasPaperlessConsent describe delivery preferences. Spend-insight records under a customerReferenceId expose insightType, insightCategory and insightStatus, and device-level alert subscriptions pair deviceTokenId with alertTypeCode values such as payment-due reminders. With authorized customer access, openData Studio turns these fields into callable open data for finance dashboards, repayment reconciliation, rewards operations and customer-notification tooling.

Screenshots

  • Capital One Canada screenshot 1
  • Capital One Canada screenshot 2
  • Capital One Canada screenshot 3
  • Capital One Canada screenshot 4

API surface

The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.

  • Password or Touch ID login

    POST /v1/maple-card/sessions osint

    Signs the cardholder in with encryptedUsername (password or Touch ID) and returns profileReferenceId, appAuthenticationToken and an optional touchIdAccessToken for the next private calls.

    Auth: No prior session. Sign-in uses encryptedUsername with encryptedPassword, or biometric credentials represented by touchIdAccessToken and touchIdAuthenticationAccessId. Session cookies from the response are required for later private calls.

    • encryptedUsername
    • encryptedPassword
    • touchIdAccessToken
    • touchIdAuthenticationAccessId
    • appAuthenticationToken
    • profileReferenceId
    • QuebecCustomer
    POST /v1/maple-card/sessions HTTP/1.1
    Accept: application/json
    Content-Type: application/json
    
    {
      "encryptedUsername": "<encryptedUsername>",
      "encryptedPassword": "<encryptedPassword>"
    }
    {
      "encryptedUsername": "<encryptedUsername>",
      "profileReferenceId": "profile_example_01",
      "appAuthenticationToken": "<appAuthenticationToken>",
      "touchIdAccessToken": "<touchIdAccessToken>",
      "QuebecCustomer": false
    }
  • Generate app authentication token

    POST /v1/maple-card/device-credentials osint

    Mints the appAuthenticationToken the wallet client presents with the login session on subsequent first-party calls.

    Auth: Device-level authentication with appVersion in the request. The returned appAuthenticationToken is used together with the customer’s login-session cookies.

    • appAuthenticationToken
    • appVersion
    POST /v1/maple-card/device-credentials HTTP/1.1
    Accept: application/json
    Content-Type: application/json
    
    {
      "appVersion": "12.34.0"
    }
    {
      "appAuthenticationToken": "<appAuthenticationToken>",
      "appVersion": "12.34.0"
    }
  • Credit cards information

    GET /v1/maple-card/profiles/{profileReferenceId}/card-overview openfinance

    Populates the home dashboard with each card’s lastFourCardNumber, currentBalance, creditLimit, availableCredit, statementBalance, minimumPaymentDueDate and cardLock under the signed-in profileReferenceId.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • profileReferenceId
    • QuebecCustomer
    • accountReferenceId
    • cardReferenceId
    • lastFourCardNumber
    • nickname
    • productType
    • productTypeCode
    • productTypeDesc
    • accountStatus
    • currentBalance
    • creditLimit
    • availableCredit
    • availableCreditUpdateIndicator
    • statementBalance
    • minimumPayment
    • minimumPaymentDueDate
    • cardLock
    GET /v1/maple-card/profiles/profile_example_01/card-overview HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "profileReferenceId": "profile_example_01",
      "QuebecCustomer": false,
      "cards": [
        {
          "accountReferenceId": "account_example_01",
          "cardReferenceId": "card_example_01",
          "lastFourCardNumber": "4412",
          "nickname": "Travel",
          "productType": "CREDIT_CARD",
          "productTypeCode": "MC",
          "productTypeDesc": "Mastercard",
          "accountStatus": "OPEN",
          "currentBalance": "412.50",
          "creditLimit": "5000.00",
          "availableCredit": "4587.50",
          "availableCreditUpdateIndicator": true,
          "statementBalance": "388.10",
          "minimumPayment": "25.00",
          "minimumPaymentDueDate": "2026-11-12",
          "cardLock": false
        }
      ]
    }
  • Posted card transactions

    GET /v1/maple-card/purchase-ledger openfinance

    Lists posted purchases for the activity feed, including merchantName, transactionAmount, transactionDate and transactionPostedDate.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • merchantName
    • transactionAmount
    • transactionDate
    • transactionPostedDate
    • postedDate
    GET /v1/maple-card/purchase-ledger HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "transactions": [
        {
          "accountReferenceId": "account_example_01",
          "merchantName": "EXAMPLE GROCERY",
          "transactionAmount": "54.19",
          "transactionDate": "2026-10-20",
          "transactionPostedDate": "2026-10-21",
          "postedDate": "2026-10-21"
        }
      ]
    }
  • Payment activity

    GET /v1/maple-card/accounts/{accountReferenceId}/payment-history openfinance

    Lists posted card payments for an accountReferenceId as paymentReferenceId, paymentAmount and the funding paymentAccountReferenceId.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • paymentReferenceId
    • paymentAccountReferenceId
    • paymentAmount
    • paymentAccountNickName
    • postedDate
    GET /v1/maple-card/accounts/account_example_01/payment-history HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "payments": [
        {
          "accountReferenceId": "account_example_01",
          "paymentReferenceId": "payment_example_01",
          "paymentAccountReferenceId": "funding_example_01",
          "paymentAmount": "388.10",
          "paymentAccountNickName": "Chequing",
          "postedDate": "2026-10-18"
        }
      ]
    }
  • Payment accounts

    GET /v1/maple-card/profiles/{profileReferenceId}/funding-sources openfinance

    Returns saved funding sources for Interac e-Transfer and DDA payments: paymentAccountNickName, paymentAccountType, lastFourDdaNumber and paymentAccountCustomerName.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • profileReferenceId
    • paymentAccountReferenceId
    • paymentAccountNickName
    • paymentAccountType
    • paymentAccountUseType
    • paymentAccountCustomerName
    • lastFourDdaNumber
    GET /v1/maple-card/profiles/profile_example_01/funding-sources HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "profileReferenceId": "profile_example_01",
      "paymentAccounts": [
        {
          "paymentAccountReferenceId": "funding_example_01",
          "paymentAccountNickName": "Chequing",
          "paymentAccountType": "CHECKING",
          "paymentAccountUseType": "PRIMARY",
          "paymentAccountCustomerName": "EXAMPLE CARDHOLDER",
          "lastFourDdaNumber": "9012"
        }
      ]
    }
  • Payment method eligibility

    POST /v1/maple-card/accounts/{accountReferenceId}/payment-options/check openfinance

    Checks which Canadian payment methods, including linked chequing and Interac options, are eligible for a paymentAmount on accountReferenceId before repayment is submitted.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • paymentAccountType
    • paymentAmount
    POST /v1/maple-card/accounts/account_example_01/payment-options/check HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    Content-Type: application/json
    
    {
      "accountReferenceId": "account_example_01",
      "paymentAccountType": "CHECKING",
      "paymentAmount": "388.10"
    }
    {
      "accountReferenceId": "account_example_01",
      "paymentAccountType": "CHECKING",
      "paymentAmount": "388.10"
    }
  • Card lock status

    GET /v1/maple-card/accounts/{accountReferenceId}/cards/{cardReferenceId}/lock-state openfinance

    Reads cardLock for a cardReferenceId so the lock/unlock control on the card tab can freeze authorizations.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • cardReferenceId
    • cardLock
    GET /v1/maple-card/accounts/account_example_01/cards/card_example_01/lock-state HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "accountReferenceId": "account_example_01",
      "cardReferenceId": "card_example_01",
      "cardLock": true
    }
  • Set card PIN

    PUT /v1/maple-card/accounts/{accountReferenceId}/pin-preference openfinance

    Writes a new PIN for the plastic keyed by accountReferenceId from the in-app PIN screen.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    PUT /v1/maple-card/accounts/account_example_01/pin-preference HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    Content-Type: application/json
    
    {
      "accountReferenceId": "account_example_01"
    }
    {
      "accountReferenceId": "account_example_01"
    }
  • Loyalty digital accounts

    GET /v1/maple-card/reward-wallets openfinance

    Loads loyalty account records with rewardsCurrency and redemptionOptionsList, including redemptionCategoryCode and redemptionAmount, for the miles and rewards hub.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • rewardsCurrency
    • redemptionOptionsList
    • redemptionCategoryCode
    • redemptionAmount
    • redemptionCurrencyCode
    GET /v1/maple-card/reward-wallets HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "accounts": [
        {
          "accountReferenceId": "account_example_01",
          "rewardsCurrency": "CAD",
          "redemptionOptionsList": [
            {
              "redemptionCategoryCode": "STATEMENT_CREDIT",
              "redemptionAmount": "50.00",
              "redemptionCurrencyCode": "CAD"
            }
          ]
        }
      ]
    }
  • Create rewards redemption order

    POST /v1/maple-card/reward-claims openfinance

    Places a rewards redemption (statement credit or travel) and returns redemptionOrderStatus plus redemptionDate.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • redemptionAmount
    • redemptionCategoryCode
    • redemptionCurrencyCode
    • redemptionDate
    • redemptionOrderStatus
    POST /v1/maple-card/reward-claims HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    Content-Type: application/json
    
    {
      "accountReferenceId": "account_example_01",
      "redemptionCategoryCode": "STATEMENT_CREDIT",
      "redemptionAmount": "50.00",
      "redemptionCurrencyCode": "CAD"
    }
    {
      "accountReferenceId": "account_example_01",
      "redemptionAmount": "50.00",
      "redemptionCategoryCode": "STATEMENT_CREDIT",
      "redemptionCurrencyCode": "CAD",
      "redemptionDate": "2026-10-26",
      "redemptionOrderStatus": "ACCEPTED"
    }
  • Account spend insights

    GET /v1/maple-card/customers/{customerReferenceId}/spending-highlights opendata

    Returns spend-insight cards for customerReferenceId as insightId, insightType, insightCategory and insightStatus.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • customerReferenceId
    • insightId
    • insightType
    • insightCategory
    • insightStatus
    GET /v1/maple-card/customers/customer_example_01/spending-highlights HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "customerReferenceId": "customer_example_01",
      "insights": [
        {
          "insightId": "insight_example_01",
          "insightType": "SPEND_CATEGORY",
          "insightCategory": "GROCERIES",
          "insightStatus": "ACTIVE"
        }
      ]
    }
  • Paperless statement preferences

    GET /v1/maple-card/accounts/{accountReferenceId}/statement-delivery opendata

    Reads paperless enrollment for an accountReferenceId: includeStatements, paperlessLob, enablePaperless and hasPaperlessConsent, used by the Go Paperless screen.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • includeStatements
    • paperlessLob
    • enablePaperless
    • hasPaperlessConsent
    • paperlessAlreadyEnrolled
    GET /v1/maple-card/accounts/account_example_01/statement-delivery HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "accountReferenceId": "account_example_01",
      "includeStatements": true,
      "paperlessLob": "CREDIT_CARD",
      "enablePaperless": true,
      "hasPaperlessConsent": true,
      "paperlessAlreadyEnrolled": true
    }
  • Credit Keeper score snapshot

    GET /v1/maple-card/credit-health/snapshot openfinance

    Returns the in-app Credit Keeper bureau snapshot as creditScoreValue, creditScoreLevel and creditScoreTitle (Equifax / TransUnion contact screens sit beside it).

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • creditScoreValue
    • creditScoreLevel
    • creditScoreTitle
    GET /v1/maple-card/credit-health/snapshot HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "creditScoreValue": 742,
      "creditScoreLevel": "GOOD",
      "creditScoreTitle": "Good"
    }
  • Canada credit-line-increase offer

    GET /v1/maple-card/accounts/{accountReferenceId}/limit-options openfinance

    Loads a Canadian credit-line-increase offer for accountReferenceId with clipOfferAmount, scoreEventDate, subModelType and offerId.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • offerId
    • clipOfferAmount
    • scoreEventDate
    • subModelType
    GET /v1/maple-card/accounts/account_example_01/limit-options HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "accountReferenceId": "account_example_01",
      "offerId": "offer_example_01",
      "clipOfferAmount": "1500.00",
      "scoreEventDate": "2026-10-01",
      "subModelType": "PREAPPROVED"
    }
  • Fulfill credit-line-increase offer

    POST /v1/maple-card/accounts/{accountReferenceId}/limit-acceptances openfinance

    Accepts the credit-line-increase offer and returns fulfillmentReferenceId for the new clipOfferAmount.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • offerId
    • clipOfferAmount
    • fulfillmentReferenceId
    POST /v1/maple-card/accounts/account_example_01/limit-acceptances HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    Content-Type: application/json
    
    {
      "accountReferenceId": "account_example_01",
      "offerId": "offer_example_01",
      "clipOfferAmount": "1500.00"
    }
    {
      "accountReferenceId": "account_example_01",
      "offerId": "offer_example_01",
      "clipOfferAmount": "1500.00",
      "fulfillmentReferenceId": "fulfillment_example_01"
    }
  • Purchase-eraser eligible transactions

    GET /v1/maple-card/accounts/{accountReferenceId}/reward-offsets openfinance

    Lists purchases that miles can erase: isPurchaseEraserEligible, isPartialEraserEligible and purchaseEraserEligibleTransactions keyed by creditCardTransactionId.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • isPurchaseEraserEligible
    • isPartialEraserEligible
    • purchaseEraserEligibleTransactions
    • creditCardTransactionId
    GET /v1/maple-card/accounts/account_example_01/reward-offsets HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "accountReferenceId": "account_example_01",
      "isPurchaseEraserEligible": true,
      "isPartialEraserEligible": false,
      "purchaseEraserEligibleTransactions": [
        {
          "creditCardTransactionId": "purchase_example_01",
          "merchantName": "EXAMPLE AIRLINE",
          "transactionAmount": "186.40"
        }
      ]
    }
  • Statement and document search

    POST /v1/maple-card/document-catalog/search opendata

    Searches statements and customer letters, returning documentId, documentType, documentName, documentDate and documentDateFormatted to identify the relevant documents.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • documentId
    • datasetId
    • documentType
    • documentName
    • documentDate
    • documentDateFormatted
    POST /v1/maple-card/document-catalog/search HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    Content-Type: application/json
    
    {
      "accountReferenceId": "account_example_01",
      "documentType": "STATEMENT"
    }
    {
      "documents": [
        {
          "documentId": "document_example_01",
          "datasetId": "statements_example",
          "documentType": "STATEMENT",
          "documentName": "October 2026 statement",
          "documentDate": "2026-10-12",
          "documentDateFormatted": "12 Oct 2026"
        }
      ]
    }
  • Activate a new plastic

    POST /v1/maple-card/accounts/{accountReferenceId}/activation-requests openfinance

    Activates a mailed plastic for accountReferenceId using lastFourCardNumber, cvv and cardsToActivate from the in-app activate-card flow.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • accountReferenceId
    • lastFourCardNumber
    • cvv
    • cardsToActivate
    POST /v1/maple-card/accounts/account_example_01/activation-requests HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    Content-Type: application/json
    
    {
      "accountReferenceId": "account_example_01",
      "lastFourCardNumber": "4412",
      "cvv": "***",
      "cardsToActivate": ["card_example_01"]
    }
    {
      "accountReferenceId": "account_example_01",
      "lastFourCardNumber": "4412",
      "cardsToActivate": ["card_example_01"]
    }
  • Mobile alert subscriptions

    GET /v1/maple-card/profiles/{profileReferenceId}/devices/{deviceTokenId}/notification-settings opendata

    Reads Canadian mobile-alert subscriptions for a deviceTokenId, including personaReferenceId, alertTypes and alertTypeCode.

    Auth: Session cookies plus appAuthenticationToken. Access is limited to the signed-in cardholder’s authorized account context.

    • profileReferenceId
    • deviceTokenId
    • personaReferenceId
    • alertTypes
    • alertTypeCode
    GET /v1/maple-card/profiles/profile_example_01/devices/device_example_01/notification-settings HTTP/1.1
    Accept: application/json
    Cookie: session=<session-cookie>
    appAuthenticationToken: <appAuthenticationToken>
    {
      "profileReferenceId": "profile_example_01",
      "deviceTokenId": "device_example_01",
      "personaReferenceId": "persona_example_01",
      "alertTypes": [
        {
          "alertTypeCode": "PAYMENT_DUE",
          "enabled": true
        }
      ]
    }

Data categories

  • balances
  • credit-limits
  • transactions
  • payments
  • rewards
  • identity
  • card-controls
  • credit-scores
  • statements
  • alerts

Where teams use this data

  • CAD balance and available-credit feed

    A Canadian PFM or collections stack pulls each plastic's currentBalance, creditLimit, availableCredit and statementBalance nightly, keyed by accountReferenceId and lastFourCardNumber, and alerts when minimumPaymentDueDate or accountStatus flips.

  • Interac and DDA payment matching

    Treasury bots bind paymentAccountReferenceId, lastFourDdaNumber and paymentAccountType to posted paymentAmount / paymentReferenceId rows so Interac e-Transfer and chequing payments reconcile without scraping the card tab.

  • Rewards redemption ops

    Loyalty desks read rewardsCurrency and redemptionOptionsList, list purchase-eraser rows by creditCardTransactionId when isPurchaseEraserEligible is true, then post redemptionAmount with redemptionCategoryCode and store redemptionOrderStatus plus redemptionDate.

  • Credit-score and line-increase ops

    An underwriting or collections desk reads creditScoreValue and creditScoreLevel from Credit Keeper, inspects clipOfferAmount / scoreEventDate / subModelType on a Canada line-increase offer, and stores fulfillmentReferenceId after the cardholder accepts.

Frequently asked questions

Which card fields does the account overview return?

Card records include accountReferenceId, cardReferenceId, lastFourCardNumber, productType, productTypeCode, productTypeDesc, accountStatus, currentBalance, creditLimit, availableCredit, availableCreditUpdateIndicator, statementBalance, minimumPayment, minimumPaymentDueDate, cardLock and nickname. The profile also carries the QuebecCustomer flag.

How are Interac and chequing payment accounts represented?

Saved funding sources include paymentAccountReferenceId, paymentAccountNickName, paymentAccountType, paymentAccountUseType, paymentAccountCustomerName and lastFourDdaNumber. Payment activity links paymentAmount and paymentReferenceId to the funding source. Payment-method eligibility considers paymentAccountType and paymentAmount before a repayment is submitted.

What data describes rewards redemption and purchase eraser?

Rewards account records contain rewardsCurrency and redemptionOptionsList, including redemptionCategoryCode, redemptionAmount and redemptionCurrencyCode. Purchase-eraser records contain isPurchaseEraserEligible, isPartialEraserEligible and purchaseEraserEligibleTransactions identified by creditCardTransactionId. Redemption confirmations add redemptionOrderStatus and redemptionDate.

How is customer access authenticated?

Sign-in uses encryptedUsername with encryptedPassword, or supported biometric credentials represented by touchIdAccessToken and touchIdAuthenticationAccessId. The customer session uses cookies together with appAuthenticationToken, and the sign-in response includes profileReferenceId. The examples show illustrative paths and mock values, not public Capital One developer endpoints; customer data requires authorized access.

Apps similar to Capital One Canada

  • RBC Mobile — RBC Royal Bank issues Avion travel, WestJet, cash-back and everyday-rewards credit cards that cardholders manage in the RBC Mobile app, including locking or reporting a lost or stolen card.
  • TD — TD Canada Trust issues Aeroplan, TD Travel Rewards, cash-back and no-annual-fee credit cards, and the TD app lets cardholders set transaction limits, block international purchases or lock the card.
  • Scotiabank — Scotiabank's Canadian cards include the Scotia Momentum cash-back Mastercard, Scene+ rewards cards and the Passport Visa Infinite travel card, with in-app activation, card management and Scotia SelectPay instalments.
  • CIBC Mobile Banking — CIBC issues Aventura, Aeroplan, cash-back, Costco and no-fee credit cards, and CIBC Online Banking and the CIBC Mobile Banking app let cardholders lock or unlock a misplaced card.
  • American Express Canada — Amex Bank of Canada issues personal flexible-rewards, cash-back and co-branded credit cards that earn Membership Rewards, with an American Express app for cardmembers in Canada.
  • Tangerine — Tangerine, a Canadian digital bank, issues the Rewards World Elite Mastercard and a no-annual-fee Money-Back World Mastercard that pays 2% cash back in up to three categories and 0.5% on other purchases.
  • MBNA — MBNA Canada issues low-interest, no-annual-fee, balance-transfer, rewards, cash-back and Amazon.ca store credit cards that customers manage through MBNA online banking and its mobile app.
  • Neo Financial — Neo Financial's Canadian Mastercard lineup includes instant virtual cards, secured credit-builder options and in-app PIN management, with World, World Elite, Cathay and United co-branded cards.

Topics

  • Capital One Canada API
  • currentBalance
  • Interac e-Transfer
  • redemptionAmount
  • CAD credit card
  • cardLock
  • accountReferenceId
  • paymentAccountReferenceId
  • creditScoreValue
  • clipOfferAmount
  • purchase eraser

Need this app's data API integrated?

We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.

  • NDA + SOW on every engagement
  • Delivery in 3–7 days
  • Payment only after acceptance
  • Work scoped to authorized use

Get a quote