Mission Lane credit-card data API
Mission Lane is Mission Lane's Android app for U.S. holders of its unsecured Visa credit cards, including Green, Silver and Gold Line products for people building or rebuilding credit. Cardholders sign in with a password and optional fingerprint or face authentication, check balances and payment due dates, activate newly issued cards, lock or unlock a card, change the PIN and add a card to Google Pay. They can make ACH or debit-card payments, set up or adjust Autopay, view PDF statements, choose paperless delivery, and link a checking account through Plaid or manual bank details. Credit-management features include a TransUnion VantageScore 3.0 view, the CLIP credit-limit increase payment-streak tracker under My Progress, annual-income and living-cost updates, credit protection and category cash-back. It serves the U.S. credit-building market alongside issuer apps such as Discover Mobile, Capital One and Credit One.
CLIP payment streaks connect currentPaymentStreak, per-statement paymentStatus and a proposed lineIncreaseAmount to evaluationDate and the current creditLimit. Credit-score records add vantageScore, fetchedAtDateTime and source, keeping the TransUnion VantageScore 3.0 reading distinct from the card's credit-limit progress. Balance records separate availableCredit, liveCurrentBalance, statementBalance and remainingMinimumDue, while statement documents carry date, id and documentUrl.
Payment and Autopay records link fundingAccountId to bankName and numberLast4, with reference, dayOfMonth and nextPaymentDate supporting reconciliation and cash-flow reminders. Purchase activity adds merchantLocation and transactionId; cash-back records track categoryRewardsRate, pendingAmount and rollingRewardsEarned. Personal-finance dashboards can combine balances and due payments, credit-building coaches can follow CLIP milestones, and accounting integrations can distinguish purchases from ACH credits. The illustrative examples use mock values; openData Studio turns these data categories into callable open data for integration projects.
Screenshots
API surface
The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.
Credit-card roster
POST
/v1/card-records/searchopenbankingLists the signed-in customer's Mission Lane Visa cards with availableCredit, currentBalance, cardLast4, lock state and product art for the home roster.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- creditCards
- availableCredit
- cardArtUrl
- cardLast4
- isLocked
- currentBalance
- id
- name
- hasAppFraud
- hasPendingAccount
POST /v1/card-records/search HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json {}{ "creditCards": [ { "id": "example-account-01", "name": "Green Line Visa", "availableCredit": 1725.0, "currentBalance": 275.0, "cardArtUrl": "<card_art_url>", "cardLast4": "4242", "isLocked": false, "hasAppFraud": false } ], "hasPendingAccount": false }Account balances and minimum due
POST
/v1/credit-accounts/balance-snapshotopenbankingReads the selected account's availableCredit and current, live, statement, past-due and remaining-minimum balance buckets for the home and payment screens.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- availableCredit
- cashAdvanceAvailableCreditLimit
- currentBalance
- liveCurrentBalance
- minimumDue
- pastDueBalance
- remainingMinimumDue
- remainingPastDueBalance
- remainingStatementBalance
- statementBalance
POST /v1/credit-accounts/balance-snapshot HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01" }{ "availableCredit": 1725.0, "cashAdvanceAvailableCreditLimit": 200.0, "currentBalance": 275.0, "liveCurrentBalance": 281.5, "minimumDue": 35.0, "pastDueBalance": 0.0, "remainingMinimumDue": 35.0, "remainingPastDueBalance": 0.0, "remainingStatementBalance": 260.0, "statementBalance": 260.0 }PDF statements
POST
/v1/account-documents/searchopenfinanceLists billed statements within a date range with each statement's date, id and documentUrl for the PDF viewer.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- statements
- date
- documentUrl
- id
POST /v1/account-documents/search HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01", "fromDate": "2026-07-01", "toDate": "2026-10-01" }{ "statements": [ { "id": "example-statement-09", "date": "2026-09-24", "documentUrl": "<statement_document_url>" }, { "id": "example-statement-08", "date": "2026-08-24", "documentUrl": "<statement_document_url>" } ] }Current bill and upcoming payments
POST
/v1/billing-plans/previewopenbankingShows the current bill's next Autopay amount and date, credit-protection enrollment status, and upcomingPayments with state and type.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- autopayConfig
- nextAutopay
- amount
- nextPaymentDate
- paymentType
- creditProtectionInfo
- status
- upcomingPayments
- date
- state
- type
POST /v1/billing-plans/preview HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01" }{ "autopayConfig": { "nextAutopay": { "amount": 35.0, "nextPaymentDate": "2026-10-24", "paymentType": "MINIMUM_DUE" } }, "creditProtectionInfo": { "status": "NOT_ENROLLED" }, "upcomingPayments": [ { "amount": 35.0, "date": "2026-10-24", "state": "SCHEDULED", "type": "AUTOPAY" } ] }Make ACH payment
POST
/v1/repayments/submitopenbankingSubmits an ACH card payment from a linked funding account using an idempotencyKey and returns the pending payment with bankName, numberLast4 and reference. The illustrative request amount is in cents; the response amount is in dollars.
Auth: Okta OIDC access token in the Authorization: Bearer header. A one-time passcode may also be required to authorize a payment.
- makePayment
- amount
- fundingAccountId
- idempotencyKey
- txMethod
- efta
- bankName
- numberLast4
- reference
- state
POST /v1/repayments/submit HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01", "amount": 4000, "fundingAccountId": "example-bank-01", "idempotencyKey": "example-payment-01", "txMethod": "ACH", "efta": "Example authorization to debit the selected checking account." }{ "makePayment": { "amount": 40.0, "fundingAccount": { "bankName": "Example Bank", "numberLast4": "6789" }, "reference": "example-confirmation-01", "state": "PENDING" } }Create Autopay
POST
/v1/recurring-repayments/enrollopenbankingEnrolls Autopay on a funding account for a dayOfMonth and paymentType, such as minimum due or statement balance, and returns confirmationId and nextPaymentDate. The illustrative request amount is in cents; the response amount is in dollars.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- createAutopay
- amount
- authorizationText
- dayOfMonth
- fundingAccountId
- paymentType
- confirmationId
- bankName
- numberLast4
- nextPaymentDate
POST /v1/recurring-repayments/enroll HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01", "amount": 3500, "authorizationText": "Example authorization for recurring ACH payments.", "dayOfMonth": 24, "fundingAccountId": "example-bank-01", "paymentType": "MINIMUM_DUE" }{ "createAutopay": { "amount": 35.0, "dayOfMonth": 24, "paymentType": "MINIMUM_DUE", "confirmationId": "example-autopay-confirmation", "fundingAccount": { "bankName": "Example Bank", "numberLast4": "6789" }, "nextPaymentDate": "2026-10-24" } }Activity feed by date range
POST
/v1/account-events/searchopendataLists posted and pending activity within a date range, distinguishing purchases with merchantLocation and transactionId from payments with funding-account details and reference.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- activities
- activityType
- amount
- date
- description
- state
- type
- merchantLocation
- transactionId
- bankName
- numberLast4
- reference
POST /v1/account-events/search HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01", "fromDate": "2026-09-01", "toDate": "2026-10-20" }{ "activities": [ { "activityType": "PURCHASE", "amount": 18.75, "date": "2026-10-14", "description": "Example Grocery", "state": "POSTED", "type": "TRANSACTION", "merchantLocation": "Example City, VA", "transactionId": "example-purchase-01" }, { "activityType": "PAYMENT", "amount": -40.0, "date": "2026-10-10", "description": "Example ACH payment", "state": "POSTED", "type": "PAYMENT", "fundingAccount": { "bankName": "Example Bank", "numberLast4": "6789" }, "reference": "example-confirmation-00" } ] }Transaction merchant detail
POST
/v1/purchase-records/detailopendataShows a posted purchase with merchant name, categoryDescription, phoneNumber and city, state and postalCode for the activity-detail screen.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- transaction
- amount
- date
- description
- merchant
- city
- postalCode
- state
- categoryDescription
- name
- phoneNumber
POST /v1/purchase-records/detail HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01", "transactionId": "example-purchase-01", "transactionDate": "2026-10-14" }{ "transaction": { "amount": 18.75, "date": "2026-10-14", "description": "Example Grocery", "state": "POSTED", "merchant": { "name": "Example Grocery", "categoryDescription": "Grocery Stores", "phoneNumber": "2025550142", "city": "Example City", "postalCode": "00000", "state": "VA" } } }TransUnion VantageScore
POST
/v1/credit-indicators/readopenfinanceProvides the customer's TransUnion VantageScore 3.0 reading on the 300–850 scale, with fetchedAtDateTime and bureau source for the credit-score view.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- creditInfo
- fetchedAtDateTime
- vantageScore
- source
POST /v1/credit-indicators/read HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01" }{ "creditInfo": { "fetchedAtDateTime": "2026-10-15T12:00:00Z", "vantageScore": 664, "source": "TRANSUNION" } }CLIP credit-limit tracker
POST
/v1/limit-progress/readopenfinanceShows the CLIP credit-limit increase tracker: on-time payment streak, per-statement paymentStatus, proposed lineIncreaseAmount and evaluationDate alongside creditLimit and Autopay enrollment.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- clipOffer
- currentPaymentStreak
- currentStatementNumber
- lineIncreaseAmount
- evaluationDate
- eligible
- status
- trackerItems
- paymentStatus
- creditLimit
- isEnrolled
POST /v1/limit-progress/read HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01" }{ "clipOffer": { "currentPaymentStreak": 3, "currentStatementNumber": 6, "lineIncreaseAmount": 300.0, "evaluationDate": "2026-11-24", "eligible": true, "status": "IN_PROGRESS", "trackerItems": [ { "paymentStatus": "ON_TIME" }, { "paymentStatus": "ON_TIME" }, { "paymentStatus": "ON_TIME" } ] }, "creditLimit": 2000.0, "isEnrolled": true }Lock card
POST
/v1/card-controls/lockopenbankingLocks the Visa card to decline authorizations and represents the resulting isLocked state and lock-control eligibility for the selected account.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- lockCard
- accountId
- isLocked
- isEligible
POST /v1/card-controls/lock HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01" }{ "lockCard": { "accountId": "example-account-01", "isLocked": true, "isEligible": true } }Funding (ACH) accounts
POST
/v1/funding-sources/searchopenbankingLists linked checking accounts used for ACH card payments, including Plaid or manual validationMethod, routing-number information, verification status and authorization expiry.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- fundingAccounts
- bankName
- numberLast4
- routingNumber
- isDefault
- isVerified
- validationMethod
- authorizationProvider
- authorizationExpiration
- status
- type
POST /v1/funding-sources/search HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json {}{ "fundingAccounts": [ { "bankName": "Example Bank", "numberLast4": "6789", "routingNumber": "<routing_number>", "isDefault": true, "isVerified": true, "validationMethod": "PLAID", "authorizationProvider": "PLAID", "authorizationExpiration": "2027-04-01", "status": "ACTIVE", "type": "CHECKING" } ] }Rewards cash-back
POST
/v1/cashback-balances/readopendataShows base rewardsRate and categoryRewardsRate alongside the payable cash-back statement-credit bucket, pendingAmount and rollingRewardsEarned.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- isRewardsCard
- rewardsRate
- categoryName
- categoryRewardsRate
- payable
- amount
- pendingAmount
- isRedeemable
- inGoodStanding
- rollingRewardsEarned
POST /v1/cashback-balances/read HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01" }{ "isRewardsCard": true, "rewardsRate": 0.01, "categoryName": "Gas", "categoryRewardsRate": 0.02, "payable": { "amount": 12.5, "pendingAmount": 1.25, "isRedeemable": true, "inGoodStanding": true, "rollingRewardsEarned": 28.75 } }Google Pay provisioning payload
POST
/v1/wallet-enrollments/prepareopenbankingPrepares an encrypted Google Pay provisioning payload and the cardholder billing address for adding the Visa card to a digital wallet.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- provisionDigitalCardGoogle
- encryptedPayload
- personName
- street1
- city
- state
- zipCode
- countryCode
- phoneNumber
POST /v1/wallet-enrollments/prepare HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01", "walletId": "<wallet_id>", "deviceId": "<device_id>" }{ "provisionDigitalCardGoogle": { "encryptedPayload": "<encrypted_wallet_payload>", "address": { "personName": "Sample Cardholder", "street1": "100 Example Street", "city": "Example City", "state": "VA", "zipCode": "00000", "countryCode": "US", "phoneNumber": "2025550142" } } }Activate card
POST
/v1/card-enrollments/activateopenbankingActivates a newly issued Visa using a tokenized CVV and expirationDate, returning activationStatus without exposing the CVV itself.
Auth: Okta OIDC access token in the Authorization: Bearer header.
- activateCardV3
- tokenizedCvv
- expirationDate
- activationStatus
POST /v1/card-enrollments/activate HTTP/1.1 Authorization: Bearer <access_token> Content-Type: application/json { "accountId": "example-account-01", "tokenizedCvv": "<tokenized_cvv>", "expirationDate": "2029-10" }{ "activateCardV3": { "activationStatus": "ACTIVATED" } }
Data categories
- balances
- statements
- payments
- credit-scores
- credit-limits
- cards
- rewards
- identity
Where teams use this data
Issuer-grade balance and due-date sync
A personal-finance or SMB ledger pulls availableCredit, liveCurrentBalance, statementBalance and remainingMinimumDue on a nightly job, then overlays upcomingPayments.date and printDueDate so cash-flow tools can warn before the Visa minimum posts.
CLIP streak coaching
A credit-building coach reads currentPaymentStreak, trackerItems.paymentStatus and lineIncreaseAmount against creditLimit, then nudges Autopay enrollment (isEligible / isEnrolled) so the next evaluationDate still qualifies for the proposed increase.
Payment-rail reconciliation
An accounting bot matches makePayment.reference and fundingAccount.numberLast4 to bank ACH debits, and uses GetActivityWithDateRange to split Transaction.merchantLocation rows from Payment rows when closing the books.
VantageScore and rewards overlay
A credit dashboard charts customer.creditInfo.vantageScore (TransUnion VantageScore 3.0) next to payable.rollingRewardsEarned and categoryRewardsRate so cardholders see whether cash-back and bureau score moved together after a statement close.
Frequently asked questions
What balance fields are covered by the Mission Lane data API?
The illustrative account-balance model includes availableCredit, cashAdvanceAvailableCreditLimit, currentBalance, liveCurrentBalance, statementBalance, minimumDue, pastDueBalance, remainingMinimumDue, remainingPastDueBalance and remainingStatementBalance. The card roster pairs availableCredit and currentBalance with cardLast4 and lock status.
What do the CLIP and TransUnion VantageScore models contain?
The tracker combines currentPaymentStreak, currentStatementNumber, trackerItems.paymentStatus, eligible, status, evaluationDate and lineIncreaseAmount with creditLimit and Autopay isEnrolled. These fields let a credit-building integration follow payment milestones and a proposed increase; they do not guarantee eligibility or approval. Yes. The creditInfo object carries vantageScore, fetchedAtDateTime and source for a TransUnion VantageScore 3.0 reading. Its scale runs from 300 to 850. The score and timestamps in the examples are mock values, not a real cardholder report.
How are payment and Autopay records organized?
An ACH payment pairs amount, fundingAccountId and idempotencyKey with a pending state and reference. Recurring-payment records include dayOfMonth, paymentType, confirmationId and nextPaymentDate. Linked funding accounts supply bankName, numberLast4, verification status and ACH authorization details for matching payments to the selected checking account.
Are these live Mission Lane endpoints, and what access would an integration need?
No. The paths and request and response examples are synthetic illustrations of card-servicing data and workflows, not production service addresses or a promise of direct issuer access. Document links and credential values are placeholders. A real integration needs the applicable authorization and access arrangements; private cardholder information is not public data. The examples use an Okta OIDC access token in the Authorization: Bearer header; a payment may also require a one-time passcode. Card activation uses a tokenized CVV, and Google Pay enrollment uses an encryptedPayload. Tokens, cardholder details and payloads shown here are placeholders, not usable credentials.
Apps similar to Mission Lane
- Capital One Mobile — Capital One's Platinum credit card is an unsecured card for building a credit score, with automatic reviews for a possible credit-limit increase and CreditWise access.
- Credit One Bank — Credit One Bank's Wander American Express metal card is a travel rewards card for fair credit that does not require a security deposit.
- Discover Mobile — Discover it Secured Cash Back is a cash-back credit card for people with bad credit who are building or rebuilding a score.
- Chase Mobile — Chase Freedom Rise is a starter credit card for students and people with limited credit that earns 1.5 percent cash back and does not require a security deposit.
- OpenSky — The OpenSky Secured Visa is a credit-building card that requires a security deposit but no credit check to apply.
- Chime — Chime's Credit Builder Secured Visa is a secured credit card that can be obtained without a credit check.
- Self — Self pairs a credit-builder loan with a secured Self Visa card so cardholders can build credit on two tradelines.
- Petal — The Petal 2 Visa is an unsecured credit-building card with no security deposit and no annual, late-payment, returned-payment or foreign-transaction fees.
Topics
- Mission Lane API
- Mission Lane credit card data
- CLIP credit-limit tracker
- TransUnion VantageScore 3.0
- Visa availableCredit
- Autopay nextPaymentDate
- ACH payment reconciliation
- cash-back rewards data
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