Marqeta Core API
REST API for card issuing, user/business management, GPA funding, transactions, authorizations, real-time decisioning, KYC/KYB, MCC controls, programs, and webhooks. Customers operate within an isolated 'program' environment.
OpenAPI Specification
openapi: 3.0.3
info:
contact:
email: support@marqeta.com
name: Marqeta
description: Marqeta's Core API endpoints, conveniently annotated to enable code
generation (including SDKs), test cases, and documentation. Currently in beta.
termsOfService: https://www.marqeta.com/api-terms
title: Core API
version: 3.0.39
servers:
- url: /v3
security:
- mqAppAndAccessToken: [
]
tags:
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the `/acceptedcountries` endpoint to manage the countries where you authorize your cardholders to transact.
name: Accepted Countries
- description: |-
The account holder group is a Marqeta platform resource that allows you to configure multiple account holders (user and/or business resources) as a group.
It allows certain settings to be selectively applied, depending on whether or not an account holder has passed verification (KYC).
You associate an account holder with an account holder group using the optional `account_holder_group_token` field in the user or business resource.
Any account holder that you do not explicitly associate with a group is automatically associated with the program's default account holder group.
The default group's name is "Default account holder group", its token is `DEFAULT_AHG`, and its configuration uses the default configuration values.
name: Account Holder Groups
- description: |-
An authorization control limits spending by specified users at specified merchants.
You can limit spending at a single merchant or at a group of merchants, and you can limit spending by a single user, users with a particular card product, or all users.
You can block spending at all merchants by default and then allow it for specific merchants, or you can allow spending at all merchants by default and block it at specific merchants.
[TIP]
See <</developer-guides/controlling-spending, Controlling Spending>> for a tutorial that walks you through the creation of a spend control, as well as links to more information about merchant category codes.
name: Authorization Controls
- description: |-
Auto reload enables you to automatically load a specified amount into an account when the account balance falls below a defined threshold.
Auto reloads execute only when the account balance falls below the trigger value due to spending.
They do not execute due to unloading of funds or because of lack of funds when a user or business is first created.
You can define auto reloads at the level of an account holder, a card product, or a program.
Each auto reload draws from a single funding source.
In the case of auto reloads defined at more than one level, the following order of precedence (first to last) determines which auto reload is executed:
. Account holder
. Card product
. Program
name: Auto Reload
- description: |-
Use the `/balances` endpoint to retrieve the following general purpose account (GPA) balance details for a user or business:
* *Ledger balance* - When using standard funding: The funds that are available to spend immediately, including funds from any authorized transactions that have not yet cleared.
When using Just-in-Time (JIT) Funding: Authorized funds that are currently on hold, but not yet cleared.
* *Available balance* - The ledger balance minus any authorized transactions that have not yet cleared.
Also known as the cardholder's purchasing power.
If you are using JIT Funding, this balance is usually 0.00.
* *Cached balance* - Not currently used.
* *Credit balance* - Not currently used.
* *Pending credits* - ACH loads that have been accepted, but for which the funding time has not yet elapsed.
name: Balances
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the `/banktransfers` endpoint to move funds between your program funding or cardholder account and an external account over the ACH Network.
This kind of bank transfer is also known as ACH origination.
You can create the following types of transfers:
* *Push* funds from your program funding or cardholder account to an external account.
* *Pull* funds from your external account into your program funding or cardholder account.
You must have an existing bank account at a US bank to fund or receive funds from your Marqeta account.
To add an external program funding source account to the Marqeta platform, send a `POST` request to the `/fundingsources/program/ach` endpoint to PUSH or PULL money from or to the Program Funding Account.
To add an external account holder funding source account to the Marqeta platform, send a `POST` request to the `/fundingsources/ach` endpoint to PUSH or PULL money from or to the Cardholder Account.
For more information on ACH funding, see <</developer-guides/ach-origination, ACH Origination>>.
name: Funding via ACH
- name: internal
- description: |-
Use the `/bulkissuances` endpoint to order physical payment cards in bulk.
For more information on cards, card products, and bulk card ordering, see <</developer-guides/about-cards, About Cards>>.
Some attributes of the `bulkissuance` object can also be defined in an associated `card` or `cardproduct` object.
If you define one of these attributes in more than one object, the Marqeta platform applies an order of precedence to determine which attribute to use at fulfillment time.
The order of precedence is as follows:
. `card`
. `bulkissuance`
. `cardproduct`
Defining an attribute in an object with higher precedence does not overwrite the same attribute in a lower-precedence object; the Marqeta platform ignores these lower-precedence attributes.
For more information on cards, see <</developer-guides/about-cards, About Cards>>.
name: Bulk Card Orders
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
// This source file is used by InfoDev to generate API reference documentation.
// File location in GitHub is:
// https://github.marqeta.com/openapi/coreapi/blob/main/openapi/businesses/openapi.yaml
A business is a type of account holder that cannot directly hold cards, but can have parent/child relationships with card-holding users.
A business can monitor and control card use by a specified group of users.
Every business has a general purpose account (GPA).
For information on how to create a user that has a child-to-parent hierarchical relationship to the business, see <</core-api/users#_create_user, Create User>>.
[NOTE]
A user can simultaneously be a child of a business and a parent of other users if the user is not configured to use the parent's account balances and the user's children are configured to use the parent's account balances.
For more information on account holders, see <</developer-guides/about-account-holders, About Account Holders>>.
name: Businesses
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the `/businesstransitions` endpoints to transition business resources between states, as well as to retrieve and list state changes for a business resource.
name: Business Transitions
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
//This source file is used by InfoDev to generate API reference documentation. File location in GitHub is:
//openapi/cardproducts/openapi.yaml
The card products resource represents the behavior and functionality of one or more cards (either physical or virtual).
For example, attributes of the card product determine whether the associated cards can be used at an ATM and/or online and whether they are currently enabled.
For physical cards, the card product determines color and other printing specifications for when the cards are manufactured and personalized.
You can optionally associate authorization controls and/or velocity controls with card products to restrict where and how associated cards are used.
If your program is Managed by Marqeta, then Marqeta will create the card products for your production environment.
Some attributes of the `cardproduct` object can also be defined in an associated `bulkissuance` or `card` object.
If you define one of these attributes in more than one object, the Marqeta platform applies an order of precedence to determine which attribute to use at fulfillment time.
The order of precedence is as follows:
. `card`
. `bulkissuance`
. `cardproduct`
Defining an attribute in an object with higher precedence does not overwrite the same attribute in a lower-precedence object; the Marqeta platform ignores these lower-precedence attributes.
For more information on cards, see <</developer-guides/about-cards, About Cards>>.
name: Card Products
- description: |-
The `card` resource represents a payment card.
Cards are derived from and controlled by the `cardproduct` resource.
For more information on cards, see <</developer-guides/about-cards, About Cards>>.
Some attributes of the `card` resource can be defined in an associated `bulkissuance` or `cardproduct` resource.
If you define one of these attributes in more than one object, the order of precedence at fulfillment time is as follows:
. `card`
. `bulkissuance`
. `cardproduct`
Defining an attribute in an object with higher precedence overrides, but does not overwrite, the attribute in a lower-precedence object.
name: Cards
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
// This source file is used by InfoDev to generate API reference documentation.
// File location in GitHub is:
// https://github.marqeta.com/openapi/coreapi/blob/main/openapi/cardtransitions/openapi.yaml
Use the `/cardtransitions` API to set the state of an existing card.
name: Card Transitions
- description: |-
Commando Mode is a fallback measure that ensures Gateway JIT-funded cards continue to function in the event that your system fails.
If your system cannot respond to the JIT Funding request, the Marqeta platform makes a decision in your place based on defined business rules.
The Marqeta platform stores any unsent webhooks for later transmission, ensuring that the card state and account balances on your system correspond with activity that occurred while Commando Mode was in effect.
You can identify transactions that were funded while Commando Mode was in effect by examining the `subnetwork` field of the transaction record.
* A `subnetwork` value of `GATEWAY_JIT` indicates that the transaction was funded through normal Gateway JIT Funding and that Commando Mode was not in effect at the time.
* A value of `MANAGED_JIT` indicates that the transaction was funded while Commando Mode was in effect.
In addition, the `standin_approved_by` field has a value of `COMMANDO_AUTO` or `COMMANDO_MANUAL` when Commando Mode is enabled for a transaction.
When `COMMANDO_MANUAL` is configured, all transactions are processed via Commando Mode.
When `COMMANDO_AUTO` is configured, Commando Mode is enabled only when a transaction times out or encounters an error.
While Commando Mode is a form of Stand-in Processing (STIP), it is different than network STIP.
Network STIP occurs when the card network cannot communicate with the Marqeta platform.
Transactions handled by network STIP include the `standin_approved_by` field with a value of `NETWORK`.
Commando Mode and Managed JIT Funding are functionally equivalent.
See <</developer-guides/about-jit-funding, About Just-in-Time Funding>> for more information.
[NOTE]
Commando Mode requires additional configuration.
To configure Commando Mode control sets, contact your Marqeta representative.
name: Commando Mode
- name: accepted countries
- name: account holder groups
- name: accounting
- name: accounts
- name: auth controls
- name: authentications
- name: auto reloads
- name: balance APIs
- name: balance caches
- name: bank transfers
- name: bulk issuances
- name: business transitions
- name: businesses
- name: businessidentitycheck
- name: caches
- name: calculation schedules
- name: card products
- name: card transitions
- name: cardholder balances
- name: cards
- name: chargebacks
- name: clearing
- name: commando modes
- name: cron jobs
- name: digital wallet provision requests
- name: digital wallet token transitions
- name: digital wallet tokens
- name: direct deposit accounts
- name: direct deposits
- name: fee charges
- name: fee refunds
- name: fees
- name: file processing
- name: funding sources
- name: Funds movement
- name: gateways
- name: Generic money transfers
- name: Google VCN digital wallet tokens
- name: GPA fund transfers
- name: gpa orders
- name: health checks
- name: Internal - BIN Pools
- name: kyblog
- name: kyc
- name: mcc groups
- name: merchantgroups
- name: Operations for digital wallet token requestor maps
- name: peer transfers
- name: ping
- name: pins
- name: post transactions
- name: program
- name: program configs
- name: program reserve
- name: program transfers
- name: real time fee groups
- name: simulate
- name: transactions
- name: user transitions
- name: users
- name: velocity controls
- name: web push provisioning
- name: webhooks
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the account cards endpoints to create and retrieve credit cards that can access the credit line on a <</core-api/credit-accounts, credit account>>.
Once a credit card is created, you can use the `/cards` endpoint to <</core-api/cards#putCardsToken, update the card>> or <</developer-guides/managing-lost-stolen-or-damaged-cards, manage lost, stolen, or damaged cards>>.
To receive webhook notifications when card transition or card action events occur, see <</core-api/event-types#_card_transition_events, Card transition events>> and <</core-api/event-types#_card_action_events, Card action events>> in Event Types.
name: Account Cards
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the account refunds endpoints to create and retrieve account refunds on Marqeta's credit platform.
You can issue account refunds to your cardholders with negative account balances.
The maximum refund amount is the amount that brings the account balance to $0.
For example, $4000 is the maximum refund amount for a -$4000 account balance.
name: Account Refunds
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the `/credit/accounts/{account_token}/rewards` endpoint to create a one-time reward on a <</core-api/credit-accounts, credit account>>.
Creating a reward triggers the creation of a <</core-api/credit-account-journal-entries, journal entry>> belonging to the `REWARD` group.
For more on reward journal entries, see <</developer-guides/about-credit-account-journal-entries#_rewards, Rewards>> in the About Credit Account Journal Entries guide.
For the reward programs that are associated with a reward policy on a bundle, see <</developer-guides/about-credit-reward-accounts/, About Credit Reward Accounts>> and <</core-api/credit-reward-global-configurations/, Reward Global Configurations>>.
name: Account Rewards
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the account transitions endpoints to create and retrieve account transitions on Marqeta's credit platform.
An account transition occurs when a <</core-api/credit-accounts, credit account>> transitions to a new status.
To receive webhook notifications when account transition events occur, see <</core-api/event-types#_credit_account_transition_events, Credit account transition events>> in Event Types.
name: Account Transitions
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Credit substatuses can be applied to credit accounts or credit account holders.
Substatuses should be applied only after verification with Customer Support and after the cardholder request for the substatus designation has been accepted.
Substatuses define specific circumstances, such as bankruptcy, hardship or fraud.
They also affect account behavior or activity, including interest accrual, authorization requests, and account termination.
Substatus downstream account actions are not always reversible for the cardholder, which means that substatuses should be applied with caution.
Use the substatus endpoints to apply or remove a substatus for a credit account or user.
Applying a substatus causes immediate downstream changes to the account.
For additional information about substatuses, see <</developer-guides/about-credit-accounts#_account-substatuses,Account substatuses>> or <</developer-guides/about-credit-accounts#_account-holder-substatuses,Account holder substatuses>> in the <</developer-guides/about-credit-accounts,About Credit Accounts>> guide.
[NOTE]
====
The substatus `SCRA` stands for "Servicemembers Civilian Relief Act."
The substatus `MLA` stands for "Military Lending Act."
====
For more information about receiving webhook notifications when account transition events occur, see <</core-api/event-types#_credit-substatus-events,Credit substatus events>> on the <</core-api/event-types,Event Types>> page.
[IMPORTANT]
====
If you are a Managed by Marqeta customer, a Marqeta customer service representative will apply the appropriate substatuses.
====
name: Credit Substatuses
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the adjustments endpoints to create and retrieve account adjustments on Marqeta's credit platform.
An account adjustment adjusts the amount of a <</core-api/credit-account-journal-entries, journal entry>> or account balance.
Creating an adjustment triggers the creation of a <</core-api/credit-account-journal-entries, journal entry>> belonging to the `ADJUSTMENT` group.
For more on adjustment journal entries, see <</developer-guides/about-credit-account-journal-entries#_adjustments, Adjustments>> in the About Credit Account Journal Entries guide.
name: Adjustments
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the credit balance refunds endpoint to issue a credit balance refund on <</core-api/credit-accounts, credit account>>.
When an account balance is negative, a balance refund can be issued to bring the balance closer to 0.
Creating a balance refund triggers the creation of a <</core-api/credit-account-journal-entries, journal entry>> belonging to the `BALANCE_REFUND` group.
For more on balance refund journal entries, see <</developer-guides/about-credit-account-journal-entries#_credit_balance_refunds, Balance refunds>> in the <</developer-guides/about-credit-account-journal-entries,About Credit Account Journal Entries>> guide.
name: Balance Refunds
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
The bundles feature on Marqeta's credit platform enables you to create and manage bundles by choosing the specific policies that make up a bundle.
A bundle must contain one document policy, credit product policy, fee policy, APR policy, and an optional reward policy.
The configurations of each policy in a bundle determine the characteristics and attributes of the bundle's associated credit accounts, reward programs, disclosures, and more.
For more on how to configure a policy, see <</core-api/credit-policies, Policies>>.
[IMPORTANT]
====
To create and manage bundles, you must use the link:https://app.marqeta.com/[Marqeta Dashboard, window="_blank"].
For more on bundles in the dashboard, see <</developer-guides/credit-programs-dashboard, Managing Credit Programs in the Marqeta Dashboard>>.
  +
The following endpoints are displayed for reference purposes only.
====
name: Bundles
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the credit accounts endpoints to create and manage accounts on Marqeta's credit platform.
A credit account centers around a single line of credit that can be accessed by one or more <</core-api/credit-account-cards, cards>>.
An account's attributes, such as the credit limit, APR, and fees, are inherited from the <</core-api/credit-policies, policies>> on its associated bundle.
For more on accounts, see <</developer-guides/about-credit-accounts, About Credit Accounts>>.
name: Credit Accounts
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the credit account disputes endpoints to create and manage disputes on a <</core-api/credit-accounts, credit account>>.
For more on disputes, see <</developer-guides/about-credit-account-disputes, About Credit Account Disputes>>.
Creating a dispute triggers the creation of a <</core-api/credit-account-journal-entries, journal entry>> belonging to the `DISPUTE` group.
For more on dispute journal entries, see <</developer-guides/about-credit-account-journal-entries#_disputes, Disputes>> in the About Credit Account Journal Entries guide.
name: Credit Account Disputes
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
[IMPORTANT]
This feature is deprecated and replaced by credit product policies, which is part of the bundles feature.
For more on policies and bundles in a credit program, see <</developer-guides/credit-programs-dashboard, Managing Credit Programs in the Marqeta Dashboard>>.
The credit products feature on Marqeta's credit platform enables you to create and manage a credit product and customize its characteristics, such as the credit line range and required fees or APRs.
Credit product characteristics determine the behaviors and attributes of associated credit accounts.
For more on credit products, see <</developer-guides/about-credit-products, About Credit Products>>.
To receive webhook notifications when product transition events occur, see <</core-api/event-types#_credit_product_transition_events, Credit product transition events>> in Event Types.
[IMPORTANT]
====
To create and manage credit products, you must use the link:https://app.marqeta.com/[Marqeta Dashboard, window="_blank"].
For more, see <</developer-guides/credit-products-dashboard, Managing Credit Products in the Marqeta Dashboard>>.
  +
The following endpoints are displayed for reference purposes only.
====
name: Credit Products
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the delinquency endpoints to retrieve details on a credit account's delinquency state and transitions.
An account's delinquency state reflects whether an account is delinquent and past due on its payments or current and up to date on its payments.
To receive webhook notifications when an account transitions between delinquent and current, see <</core-api/event-types#_credit_account_delinquency_state_transition_events, Credit account delinquency state transition events>> in Event Types.
name: Delinquency
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the journal entries endpoints to retrieve journal entries made on an <</core-api/credit-accounts, account>> on Marqeta's credit platform.
A journal entry is a record of an entry made on an account journal, such as a purchase transaction, fee, adjustment, and more.
For more on the different types of journal entries, see <</developer-guides/about-credit-account-journal-entries, About Credit Account Journal Entries>>.
Journal entries originate when a journal entry event occurs, such as a cardholder making a purchase or an account holder making a payment.
To receive webhook notifications when journal entry events occur, see <</core-api/event-types#_credit_journal_entry_events, Credit journal entry events>> in Event Types.
name: Journal Entries
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
[IMPORTANT]
====
This feature is deprecated and replaced by journal entries.
  +
For documentation on journal entries, see:
  +
* <</developer-guides/about-credit-account-journal-entries, About Credit Account Journal Entries>> - Developer guide
* <</core-api/credit-account-journal-entries, Journal Entries>> - API reference
* <</core-api/event-types#_credit_journal_entry_events, Credit journal entry event types>> - Webhook notifications.
====
Use the `/credit/accounts/{account_token}/ledgerentries` endpoint to retrieve ledger entries made on an <</core-api/credit-accounts, account>> on Marqeta's credit platform.
A ledger entry is a record of an entry made on an account ledger, such as a purchase transaction, fee, adjustment, and more.
For more on the different types of ledger entries, see <</developer-guides/about-credit-account-ledger-entries, About Credit Account Ledger Entries>>.
Ledger entries originate when a ledger entry event occurs, such as a cardholder making a purchase or an account holder making a payment.
To receive webhook notifications when ledger entry events occur, see <</core-api/event-types#_credit_ledger_entry_events, Credit ledger entry events>> in Event Types.
name: Ledger Entries
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
The Marqeta credit platform's policies feature enables you to customize the configurations of policies for documents (such as disclosures), credit products, fees, APRs, and rewards.
You can choose the specific policies to add to a bundle that contain the exact configurations needed to launch a new credit program or help manage an existing one.
The configurations of each policy in a bundle determine the characteristics and attributes of the bundle's associated credit accounts, reward programs, disclosures, and more.
For more on how to create a bundle, see <</core-api/credit-bundles, Bundles>>.
[IMPORTANT]
====
To create and manage policies, you must use the link:https://app.marqeta.com/[Marqeta Dashboard, window="_blank"].
For more on policies in the dashboard, see <</developer-guides/credit-programs-dashboard, Managing Credit Programs in the Marqeta Dashboard>>.
  +
The following endpoints are displayed for reference purposes only.
====
name: Policies
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the payment schedule endpoints to create and retrieve payment schedules and payment schedule transitions on a <</core-api/credit-accounts, credit account>>.
A payment schedule allows you to schedule a one-time or recurring payment on a credit account.
For more on payments, see <</developer-guides/about-credit-account-payments, About Credit Account Payments>>.
To receive webhook notifications when ACH payment transition events occur, see <</core-api/event-types#_credit_account_payment_transition_events, Credit account payment transition events>> in Event Types.
Making a payment on a payment schedule triggers the creation of a <</core-api/credit-account-journal-entries, journal entry>> belonging to the `PAYMENT` group.
For more on payment journal entries, see <</developer-guides/about-credit-account-journal-entries#_payments, Payments>> in the About Credit Account Journal Entries guide.
name: Payment Schedules
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the payment sources endpoint to link an external payment source to an <</core-api/credit-accounts, account>> on Marqeta's credit platform.
This enables account holders to use the linked payment source to make payments toward their account balance.
name: Payment Sources
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the payments endpoints to create and retrieve payments made on a <</core-api/credit-accounts, credit account>>, release payment holds, or transition payment statuses.
A payment is an amount paid toward an account balance to reduce the total amount owed on the account.
For more on payments, see <</developer-guides/about-credit-account-payments, About Credit Account Payments>>.
To receive webhook notifications when ACH payment transition events occur, see <</core-api/event-types#_credit_account_payment_transition_events, Credit account payment transition events>> in Event Types.
Creating a payment triggers the creation of a <</core-api/credit-account-journal-entries, journal entry>> belonging to the `PAYMENT` group.
For more on payment journal entries, see <</developer-guides/about-credit-account-journal-entries#_payments, Payments>> in the About Credit Account Journal Entries guide.
name: Payments
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the Credit Program Gateways endpoints to create, retrieve, and update Program Gateways for your credit program.
A Program Gateway allows you to exchange messages with Marqeta's credit platform regarding decisions on transaction authorizations.
For more on Program Gateways, see <</developer-guides/about-credit-program-gateways, About Credit Program Gateways>>.
name: Program Gateways
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
Use the statements endpoints to retrieve statement information or statement files for a <</core-api/credit-accounts, credit account>>.
An account statement contains a summary of account activity that occurred during a billing cycle.
For more on statements, see <</developer-guides/about-credit-account-statements, About Credit Account Statements>>.
To receive a webhook notification when a statement is created, see <</core-api/event-types#_credit_account_statement_event, Credit account statement event>> in Event Types.
name: Statements
- description: |-
// Conditional snippet for beta or internal content
include::../../maturity-admonition-banner.adoc[]
// This source file is used by InfoDev to generate API reference documentation.
// File location in GitHub is: openapi/feecharges/openapi.yaml
A fee charge moves funds from
# --- truncated at 32 KB (1815 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/marqeta/refs/heads/main/openapi/marqeta-core-api-openapi.yml