/
30 minute read
November 23, 2021

Event Types

Hidden

Account holder transition events

Account holder transition events include activities such as a user or business being created, suspended, or closed. These activities transition a user’s or business' status.

Account holder transition notifications contain detailed information about the events. They are sent as account holder transition events occur.

Each notification contains a status field that categorizes the account holder transition event. The following table describes each account holder status. Values in the Status column are the literal values of the notification’s status field. When configuring a webhook to capture these events, you must prefix this with usertransition or businesstransition (for example, usertransition.active).

Status Description

unverified

User or business was created in an unverified status due to KYC.

limited

User or business was created in a limited status due to KYC.

active

User or business was created in an active status due to KYC, or passed KYC after being unverified or limited.

suspended

User or business was suspended.

closed

User or business was closed.

Account holder transition notifications are structured as an array within a users or businesses element. Multiple notifications can be included in a single notification message. The structure of each individual notification is identical to that of a usertransition or businesstransition object returned by the /usertransitions and /businesstransitions endpoints, respectively.

The following example shows a notification message containing a business transition notification, indicating the business was closed.

Copied

Is this helpful?

Yes
No

For more information about the usertransitions object, see Users. For more information about the businesstransitions object, see Businesses.

Direct deposit account transition events

Direct deposit account transition events include activities such as a direct deposit account being activated, suspended, or terminated. Updating the account’s state field triggers these event notifications.

Direct deposit account transition notifications are sent as the corresponding transition events occur. Each notification contains a state field that indicates the account’s new state. The following table describes the possible values of the state field within a directdepositaccounttransition event. Values in the State column are the literal values of the notification’s state field. When configuring a webhook to capture these events, you must prefix this with directdepositaccounttransition (for example, directdepositaccounttransition.active).

State Description

ACTIVE

The direct deposit account is functional, and allows debit and credit transactions including ACH. Transitions to the SUSPENDED or TERMINATED states are permitted.

SUSPENDED

The direct deposit account is temporarily non-functional. When in this state, all credits and debits including ACH should be processed. Transitions to the ACTIVE or TERMINATED states are permitted.

TERMINATED

The direct deposit account is permanently non-functional and cannot transition to any other state. When in this state, all credits including ACH should be processed; all debits should be rejected.

The following example shows a directdepositaccounttransition.suspended event.

Copied

Is this helpful?

Yes
No

For more information about the /depositaccounts/transitions endpoint, see Direct Deposits.

Card transition events

The following applies to both debit and credit (beta) cards.

Note
The credit cards feature is currently in limited-availability beta and subject to change. To learn more about the beta program for this feature, contact your Marqeta representative.

Card transition events include activities such as a card being activated/deactivated, ordered, or shipped. From a technical point of view, they are activities that cause the transition of a card’s state or fulfillment_status field.

Card transition notifications are sent as card transition events occur and contain detailed information about the events.

Each notification contains a type field that categorizes the card transition event. The following table describes each card transition event type. The values in the Type column are the literal values of the notification’s type field. When configuring a webhook to capture debit card events, you must prefix this type with cardtransition (for example, cardtransition.fulfillment.issued). To capture credit card events, you must add an additional prefix of credit (for example, credit.cardtransition.fulfillment.issued).

Type Description

fulfillment.digitally_presented

Card was digitally presented using the /cards/{token}/showpan endpoint.

fulfillment.issued

Card was created/issued.

fulfillment.ordered

Card was ordered from card fulfillment provider.

fulfillment.rejected

Card was rejected by card fulfillment provider.

fulfillment.reordered

Card was reordered from card fulfillment provider.

fulfillment.shipped

Card was shipped by card fulfillment provider. This field appears only if it is provided by the card fulfillment provider.

state.activated

Card was activated.

state.reinstated

Card was reinstated from a suspended state.

state.suspended

Card was suspended.

state.terminated

Card was terminated.

pin.changed

Card PIN was changed.

This field is for debit cards only.

pin.set

Card PIN was set.

This field is for debit cards only.

pin.reveal

Card PIN was revealed to the cardholder.

This field is for debit cards only.

Card transition notifications are structured as an array within a cards element for debit cards, or a creditcardtransitions element for credit cards. Multiple notifications can be included in a single notification message. The structure of each individual notification is identical to that of a cardtransition object returned by the /cardtransitions endpoint.

The following debit example shows a notification message containing two debit card transition notifications: one for the issuance of a card, and one for the activation of that card.

Copied

Is this helpful?

Yes
No

The following credit card example shows a notification message containing the activation of a credit card.

Copied

Is this helpful?

Yes
No

For more information about the cardtransitions and creditcardtransitions object, see Cards.

Card action events

Card action events include PIN set, PIN change, and PIN reveal actions. Card action notifications are sent as card action events occur and contain detailed information about the events.

Each notification contains a type field that categorizes the card action event. The following table describes each card action event type. The values in the Type column are the literal values of the notification’s type field. When configuring a webhook to capture these events, you must prefix this type with cardaction (for example, cardaction.pin.set).

Type Description

pin.changed

Card PIN was changed.

pin.reveal

Card PIN was revealed.

pin.set

Card PIN was set.

The following example shows a notification message containing a notification that a PIN was set for a card.

Copied

Is this helpful?

Yes
No

Chargeback transition events

Chargeback transition events mark the progress of disputes through the arbitration process. From a technical point of view, chargeback transition events cause the transition of a chargeback object’s state field.

The chargeback object represents a completed transaction that has been disputed by the issuer. In order for the dispute to be resolved, the chargeback must pass through an arbitration process consisting of multiple phases. Each phase of the arbitration process is represented by a chargebacktransition object of a particular type. For example, the creation of a new chargeback incidentally creates a chargebacktransition of type initiated. After creating a chargeback, you can explicitly move it from one arbitration phase to another by creating a chargebacktransition of the appropriate type. Chargebacks do not follow a prescribed path through the arbitration process.

Chargeback transition notifications are sent as chargeback transition events occur and contain detailed information about the events.

Each notification contains a type field that categorizes the chargeback transition event. The following table describes each chargeback transition event type. The values in the Type column are the literal values of the notification’s type field. When configuring a webhook to capture these events, you must prefix this type with chargebacktransition (for example, chargebacktransition.representment).

Type Description

initiated

The chargeback has been created. Funds to cover the disputed charges have been credited to the cardholder’s account if the credit_user field was true or unspecified at the time of creation.

representment

The case is in representment (also known as second presentment). The gateway/acquirer has disputed the chargeback. In some cases, representment does not occur.

prearbitration

The case is in prearbitration (also known as arbitration chargeback). Upon receipt of a dispute from the gateway/acquirer (representment), the issuer can submit the chargeback a second time, possibly with more or different information. Only relevant chargebacks assume this status.

arbitration

The case is in arbitration. When a gateway/acquirer disputes a chargeback, the issuer can submit the case to the card network for arbitration after either the first or second (prearbitration) chargeback. In arbitration, the card network decides who wins the chargeback case.

case.won

The chargeback case is closed; Marqeta won.

case.lost

The chargeback case is closed; Marqeta lost.

network.rejected

The card network rejected the chargeback submission.

written.off.issuer

Can be transitioned to only from case.lost or network.rejected. The chargeback is credited to the GPA of the user or business and Marqeta absorbs the cost.

written.off.program

Can be transitioned to only from case.lost or network.rejected. The chargeback is credited to the GPA of the user or business and the Marqeta customer absorbs the cost through a debit from the program funding source.

Chargeback transition notifications are structured as an array within a chargebacktransitions element. Multiple notifications can be included in a single notification message.

The following example shows a notification message containing two chargeback transition notifications:

Copied

Is this helpful?

Yes
No

Credit account statement event (beta)

Note
This feature is currently in limited-availability beta and subject to change. To learn more about the beta program for this feature, contact your Marqeta representative.

The credit account statement event occurs when a statement is generated on the billing cycle day and contains detailed information about the statement, including the opening date, closing date, closing balance, and more.

When configuring your webhook to subscribe to the credit account statement event, set the events value to credit.accountstatement.created. Marqeta sends a webhook notification as soon as a credit account statement event occurs. (To receive notifications for all credit events, configure your webhook to capture credit.* events. For more, see Webhooks Management.)

The following example shows a credit.accountstatement.created event.

Copied

Is this helpful?

Yes
No

For more information about the creditaccountstatements object, see Retrieve account statement summary.

Credit account transition events (beta)

Note
This feature is currently in limited-availability beta and subject to change. To learn more about the beta program for this feature, contact your Marqeta representative.

Credit account transition events include activities such as a credit account being activated, unactivated, suspended, or terminated. From a technical point of view, they are activities that cause the transition of a credit account’s status field.

Credit account transition notifications are sent as the credit account transition events occur and contain detailed information about the events.

Each notification contains a status field that indicates the account’s new status. The following table describes each credit account status. Values in the Status column are the literal values of the notification’s status field. Values in the Type field are the literal webhook event type. When configuring a webhook to capture these events, you must prefix the event type with credit.accounttransition (for example, credit.accounttransition.status.activated).

Status Type Description

UNACTIVATED

status.unactivated

The unactivated credit account is awaiting activation by the account holder. Transition to ACTIVATED is permitted.

ACTIVE

status.activated

The activated credit account is functional and allows account activity such as credit transactions. Transitions to SUSPENDED and TERMINATED are permitted.

SUSPENDED

status.suspended

The suspended credit account is temporarily non-functional. Transitions to ACTIVATED or TERMINATED are permitted.

TERMINATED

status.terminated

The terminated credit account is permanently non-functional and cannot transition to another status. This is a terminal status.

To receive notifications for all credit events, configure your webhook to capture credit.* events. For more, see Webhooks Management.

The following example shows a credit.accounttransition.status.activated event.

Copied

Is this helpful?

Yes
No

For more information about the creditaccounttransitions object, see Retrieve account transition.

Credit account payment transition events (beta)

Note
This feature is currently in limited-availability beta and subject to change. To learn more about the beta program for this feature, contact your Marqeta representative.

The following applies to ACH payments on credit accounts only.

Credit account payment transition events include activities such as a payment being initiated, submitted, or returned on a credit account. From a technical point of view, they are activities that cause the transition of a payment’s status field.

Payment transition notifications are sent as payment transition events occur and contain detailed information about the events.

Each notification contains a status field that categorizes the payment transition event. The following table describes each payment status. Values in the Status column are the literal values of the notification’s status field. When configuring a webhook to capture these events, you must prefix this with credit.paymenttransition (for example, credit.paymenttransition.initiated).

Status Description

initiated

Payment was initiated.

pending

Payment was successfully created.

processing

Payment is being processed by the ACH processor.

submitted

Payment was submitted to the bank.

completed

Payment is completed.

returned

Payment was returned.

refunded

Payment was refunded.

cancelled

Pending payment was canceled using the Transition account payment status API.

To receive notifications for all credit events, configure your webhook to capture credit.* events. For more, see Webhooks Management.

The following example shows a credit.paymenttransition.completed event.

Copied

Is this helpful?

Yes
No

For more information about the creditpaymenttransitions object, see Transition account payment status.

Credit ledger entry events (beta)

The following applies to credit ledger entry events only. For debit transactions, see Transaction events.

Note
This feature is currently in limited-availability beta and subject to change. To learn more about the beta program for this feature, contact your Marqeta representative.

Credit ledger entry events include activities on a credit account such as purchase authorizations, purchase authorization clearings, refunds, credit balance refunds, adjustments, fees, interest, rewards, and payments. Although you might think of a purchase authorization and purchase authorization clearing as two parts of the same conceptual ledger entry, the Marqeta platform treats each ledger entry-related message exchange as a separate ledger entry event with a unique identifying token.

Ledger entry notifications are sent in real time as ledger entry events occur and contain detailed information about the events.

All ledger entry notifications contain a type field that categorizes the ledger entry event. The following table lists all possible values for the type field. The values in the Type column are the literal values of the notification’s type field. When configuring a webhook to capture ledger entry events, you must prefix this type with credit.ledgerentry (for example, credit.ledgerentry.authorization).

Type Description

authorization

Funds hold due to card usage. Temporary transaction type. Requires settlement.

authorization.incremental

Increases the amount of a previous authorization by adding to it without replacing it.

refund.authorization

Authorization for a purchase return. Temporary transaction type.

authorization.clearing

Completes an authorization.

authorization.reversal

Reverses or drops an authorization not due to elapsed time.

authorization.advice

Replaces the amount of an existing authorization. Temporary transaction type. Requires settlement.

account.adjustment

Ghost adjustment was applied.

account.adjustment.fee

Fee adjustment was applied.

account.adjustment.interest

Interest adjustment was applied.

account.adjustment.purchase

Purchase adjustment was applied.

account.adjustment.reward

Reward adjustment was applied.

account.balance.refund

Credit balance refund was applied.

account.fee.latepayment

Late payment fee was applied.

account.fee.minimum.interest

Minimum interest fee was applied.

account.fee.returnpayment

Returned payment fee was applied.

account.interest

Interest charges were applied.

account.payment.canceled

Payment was canceled.

account.payment.completed

Payment was completed.

account.payment.pending

Payment is pending.

account.payment.refunded

Payment was refunded

account.payment.returned

Payment was returned.

account.reward.cashback

Rewards were posted.

authorization

Funds hold due to card usage. Temporary transaction type. Requires settlement.

authorization.advice

Replaces the amount of an existing authorization. Temporary transaction type. Requires settlement.

authorization.clearing

Completes an authorization.

authorization.incremental

Increases the amount of a previous authorization by adding to it without replacing it.

authorization.reversal

Reverses or drops an authorization not due to elapsed time.

authorization.reversal.issuerexpiration

Reverses or drops an authorization due to elapsed time; initiated by Marqeta.

original.credit.authorization

Original credit transaction (OCT) authorization for disbursing funds to a credit card.

original.credit.authorization.reversal

Reverses the financial impact of an OCT authorization.

original.credit.authorization.clearing

Completes an OCT authorization.

original.credit.auth_plus_capture

Single-message OCT for disbursing funds to a credit card.

original.credit.auth_plus_capture.reversal

Reverses the financial impact of a single-message OCT.

refund

Refunds a cardholder’s transaction.

refund.authorization

Authorization for a purchase return. Temporary transaction type.

refund.authorization.clearing

Completes a purchase return authorization.

refund.authorization.reversal

Reverses a purchase return authorization.

To receive notifications for all credit events, configure your webhook to capture credit.* events. For more, see Webhooks Management.

Ledger entry notifications are structured as an array within a creditledgerentries element for credit ledger entries.

The following is a sample purchase credit ledger entry notification. The detail_object contains the purchase details, in this case. However, fields in the detail_object vary based on the group value. For example, purchases return purchase details; adjustments return adjustment details; interest returns interest details.

The following example shows a credit.ledgerentry.authorization event.

Copied

Is this helpful?

Yes
No

For more information about the creditledgerentries object, see Retrieve account ledger entry.

Credit product transition events (beta)

Note
This feature is currently in limited-availability beta and subject to change. To learn more about the beta program for this feature, contact your Marqeta representative.

Credit product transition events include activities such as a credit product being activated, pending approval, sent for revision, or rejected. These activities transition a credit product’s status.

Credit product transition notifications contain detailed information about the events. They are sent as credit product transition events occur.

Each notification contains a status field that categorizes the credit product transition event. The following table describes each credit product status. Values in the Status column are the literal values of the notification’s status field. Values in the Type field are the literal webhook event type. When configuring a webhook to capture these events, you must prefix the event type with credit.producttransition (for example, credit.producttransition.status.activated).

Status Type Description

ACTIVE

status.activated

Credit product was activated.

PENDING APPROVAL

status.pendingapproval

Credit product was created and is now pending approval.

SENT FOR REVISION

status.sentforrevision

Credit product was sent for revision.

REJECTED

status.rejected

Credit product was rejected.

To receive notifications for all credit events, configure your webhook to capture credit.* events. For more, see Webhooks Management.

The following example shows a credit.producttransition.state.activated event.

Copied

Is this helpful?

Yes
No

For more information about credit products, see Credit Products.

Commando Mode transition events

Commando Mode transition events include enabling and disabling a Commando Mode control set for the associated program gateway funding source. These activities transition the current_state.commando_enabled field of a specific Commando Mode control set.

Commando Mode transition notifications are sent as transition events occur and contain detailed information about the events. When configuring a webhook to capture these events, you must prefix the event type (such as enabled or disabled) with commandomodetransition. For example, to capture when a Commando Mode control set is enabled, you must configure a webhook for the commandomodetransition.enabled event.

The following table describes each Commando Mode transition event type.

Type Description

enabled

Indicates that a Commando Mode control set was enabled.

disabled

Indicates that a Commando Mode control set was disabled.

The following example shows a notification message containing a Commando Mode transition notification, indicating the Commando Mode control set was disabled.

Copied

Is this helpful?

Yes
No

For more information about the commandomodes object, see Commando Mode.

Digital wallet token transition events

The following applies to both debit and credit (beta) digital wallet tokens.

Note
The credit digital wallet tokens feature is currently in limited-availability beta and subject to change. To learn more about the beta program for this feature, contact your Marqeta representative.

Digital wallet token transition events include activities such as a digital wallet token being requested, activated, or terminated. From a technical point of view, they are activities that cause the transition of a token’s state or fulfillment_status field.

Digital wallet token transition notifications are sent as digital wallet token transition events occur and contain detailed information about the events.

Each notification contains a type field that categorizes the digital wallet token transition event. The following table describes each digital wallet token transition event type. The values in the Type column are the literal values of the notification’s type field. When configuring a webhook to capture debit digital wallet token events, you must prefix this type with digitalwallettokentransition (for example, digitalwallettokentransition.fulfillment.requested). To capture credit digital wallet token events, you must add an additional prefix of credit (for example, credit.digitalwallettokentransition.fulfillment.requested).

Type Description

fulfillment.requested

Indicates that a token was requested and provisioning is pending.

state.request_declined

Indicates that token provisioning was rejected. The state of the token cannot be further modified.

state.activated

Indicates that the token has been provisioned and is active.

state.suspended

Indicates that the token has been suspended.

state.reinstated

Indicates that the token has been reactivated from a suspended state.

state.terminated

Indicates that the token has been terminated. The state of the token cannot be further modified.

card.swap

A card was activated (the card state transitioned from UNACTIVATED to ACTIVE), and all existing digital wallet tokens owned by the user and having a state of REQUESTED, ACTIVE, or SUSPENDED were moved to the new card.

Note
The token-related event type token.activation-request is categorized as a transaction event and is documented in the Transaction events section.

Digital wallet token transition notifications are structured as an array within a digitalwallettokentransitions element for debit tokens, or a creditdigitalwallettokentransitions for credit tokens. Multiple notifications can be included in a single notification message. The structure of each individual notification is identical to that of a digitalwallettokentransition object returned by the /digitalwallettokentransitions API endpoint.

The following example shows a notification message containing two digital wallet token transition notifications: one requesting a token, and one for the activation of that token.

Copied

Is this helpful?

Yes
No

For more information about the digitalwallettokentransitions and creditdigitalwallettokentransitions object, see Digital Wallets Management.

KYB results event

The kybresults event returns the results of a KYC verification request for a business when the BUSINESS component could not be verified in the allotted time. In such cases, the KYC request returns a status of VENDOR_PENDING, and the relevant BUSINESS component also returns an outcome of VENDOR_PENDING.

Note
The VENDOR_PENDING status only applies to the BUSINESS component, not to the PROPRIETOR or BENEFICIAL_OWNER components. Therefore, the kybresults event only returns information about the BUSINESS component.

Marqeta sends kybresults events as soon as the KYC vendor returns the final verification for the business KYC verification request.

The following example shows a kybresults event that returned a successful KYC result for a business. The token field includes the original KYC request token from the POST /kyc action. See Perform KYC for information about the POST /kyc action.

Copied

Is this helpful?

Yes
No

For more information about the business.results object, see the business result array.

Transaction events

The following applies to debit transaction events only. For credit ledger entries, see Credit ledger entry events.

Transaction events include activities such as authorizations, authorization clearings, and refunds. Although you might think of an authorization and authorization clearing as two parts of the same conceptual transaction, the Marqeta platform treats each transaction-related message exchange as a separate transaction event with a unique identifying token.

Transaction notifications are sent in real time as transaction events occur; they contain detailed information about the events.

All transaction notifications contain a type field that categorizes the transaction event. The following table lists all possible values for the type field. The table describes each type, indicates the objects potentially included in that transaction type, and lists the transaction types that could potentially complete it. The values in the Type column are the literal values of the notification’s type field. When configuring a webhook to capture these events, you must prefix this type with transaction (for example, transaction.authorization).

The response.code field describes the outcome of the attempted transaction. For more information on transaction outcomes, see the transaction response codes table on the Transactions API reference page.

See all transaction response fields in the Transaction field descriptions.

Type Description

account.funding.authorization

Funds hold for an account funding transaction (AFT).

Temporary transaction type.

Possibly completed by: account.funding.authorization.clearing

account.funding.authorization.clearing

Completes an AFT authorization (account.funding.authorization).

Final transaction type.

account.funding.auth_plus_capture

Funds hold for a single-message AFT.

Final transaction type.

account.funding.authorization.reversal

Cancels and reverses an AFT authorization (account.funding.authorization).

Final transaction type.

account.funding.auth_plus_capture.reversal

Reverses and cancels a single-message AFT (account.funding.auth_plus_capture).

Final transaction type.

authorization

Funds hold due to card usage.

Temporary transaction type. Requires settlement.

Possibly completed by: authorization.advice, authorization.reversal, authorization.reversal.issuerexpiration, authorization.clearing

Possibly included objects: card_acceptor, gpa, user.metadata, digital_wallet_token

authorization.advice

Decreases the amount of an existing authorization (authorization).

Temporary transaction type. Requires settlement. Must be honored.

Possibly completed by: authorization.reversal, authorization.reversal.issuerexpiration, authorization.clearing

Possibly included objects: card_acceptor, gpa, user.metadata, digital_wallet_token

authorization.atm.withdrawal

In the EU, authorization for withdrawing cash at an ATM. In the US, this event indicates that the cardholder got cash from a cashier rather than an ATM.

Temporary transaction type.

Possibly completed by: authorization.clearing.atm.withdrawal

authorization.cashback

Authorization for cash back requested at a point-of-sale terminal.

Temporary transaction type.

Possibly completed by: authorization.clearing.cashback

authorization.clearing

Completes an authorization (authorization).

Final transaction type.

Possibly included objects: card_acceptor, gpa, user.metadata, digital_wallet_token

authorization.clearing.atm.withdrawal

Completes an authorization for withdrawing cash at an ATM (authorization.atm.withdrawal).

Final transaction type.

authorization.clearing.cashback

Completes an authorization for cash back requested at a point-of-sale terminal (authorization.cashback).

Final transaction type.

authorization.clearing.chargeback

Marqeta-initiated chargeback.

Possibly completed by: authorization.clearing.chargeback.reversal, authorization.clearing.chargeback.completed

Possibly included objects: gpa, chargeback, user.metadata

Possible states: INITIATED, PREARBITRATION, ARBITRATION,

Ledger impact: Positive if credit_user is true; none if credit_user is false.

authorization.clearing.chargeback.completed

Completes a Marqeta-initiated chargeback (authorization.clearing.chargeback).

Possibly included objects: gpa, chargeback, user.metadata

Possible states: CASE_WON

Ledger impact: Positive.

authorization.clearing.chargeback.provisional.credit

Provides a credit by moving a chargeback (authorization.clearing.chargeback) from the workflow for non-provisional credit to provisional credit.

Final transaction type. Requires settlement.

Possibly included objects: gpa, chargeback, user.metadata

authorization.clearing.chargeback.provisional.debit

Removes the initial credit by moving a chargeback (authorization.clearing.chargeback) from the workflow for provisional credit to non-provisional credit.

Final transaction type. Requires settlement.

Possibly included objects: gpa, chargeback, user.metadata

authorization.clearing.chargeback.reversal

Reverses a rejected, Marqeta-initiated chargeback (authorization.clearing.chargeback).

Possibly included objects: gpa, chargeback, user.metadata

Possible states: CASE_LOST, NETWORK_REJECTED

Ledger impact: Negative if credit_user is true; none if credit_user is false.

authorization.clearing.chargeback.writeoff

Writes off the chargeback (authorization.clearing.chargeback) and credits the account holder while Marqeta or its customer absorbs the cost.

Final transaction type.

Possibly included objects: gpa, chargeback, user.metadata

Possible states: WRITTEN_OFF_PROGRAM, WRITTEN_OFF_ISSUER

Ledger impact: Positive.

authorization.clearing.quasi.cash

Completes an authorization at a point-of-sale terminal for items equivalent to cash (authorization.quasi.cash), such as traveler’s checks, money orders, foreign currency, or gaming chips.

Final transaction type.

authorization.clearing.representment

Merchant dispute of a Marqeta-initiated chargeback (authorization.clearing.chargeback).

Possible states: REPRESENTMENT

Ledger impact: Negative if credit_user is true; none if credit_user is false and representment amount equals original amount; positive if credit_user is false and representment amount is less than original amount.

Possibly included objects: gpa, chargeback, user.metadata

authorization.incremental

Increases the amount of a previous authorization (authorization) by adding to it without replacing it.

Temporary transaction type. Requires settlement.

Possibly completed by: authorization.reversal

Possibly included objects: card_acceptor, gpa, user.metadata, digital_wallet_token

authorization.quasi.cash

Authorization at a point-of-sale terminal for items equivalent to cash, such as traveler’s checks, money orders, foreign currency, or gaming chips.

Temporary transaction type.

Possibly completed by: authorization.clearing.quasi.cash

authorization.reversal

Reverses or drops an authorization (authorization) due to elapsed time.

Possibly included objects: card_acceptor, gpa, user.metadata, digital_wallet_token

authorization.reversal.issuerexpiration

Reverses or drops an authorization (authorization) due to elapsed time; initiated by Marqeta.

Possibly included objects: card_acceptor, gpa, user.metadata, digital_wallet_token

authorization.standin

The card network declined an (authorization) due to no response from Marqeta.

Final transaction type.

Possibly included objects: card_acceptor, gpa, user.metadata, digital_wallet_token

directdeposit.credit

Credits funds to a deposit account.

Final transaction type.

State of associated direct deposit record: APPLIED

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.credit.pending

Pending credit of funds to a deposit account.

Temporary transaction type.

State of associated direct deposit record: PENDING

Possibly completed by directdeposit.credit, directdeposit.credit.reversal, directdeposit.credit.reject

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.credit.reject

Rejects a crediting of funds to a deposit account (directdeposit.credit).

Final transaction type.

State of associated direct deposit record: REJECTED

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.credit.pending.reversal

Reverses a pending credit of funds to a deposit account (directdeposit.credit.pending).

Final transaction type.

State of associated direct deposit record: REVERSED

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.credit.reversal

Reverses a credit of funds to a deposit account (directdeposit.credit).

Final transaction type.

State of associated direct deposit record: REVERSED

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.debit

Debits funds from a deposit account.

Final transaction type.

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.debit.pending

Pending debit of funds from a deposit account.

Temporary transaction type.

State of associated direct deposit record: PENDING

Possibly completed by: directdeposit.debit, directdeposit.debit.reversal, directdeposit.debit.reject

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.debit.reject

Rejects a debit of funds from a deposit account (directdeposit.debit).

Final transaction type.

State of associated direct deposit record: REJECTED

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.debit.reversal

Reverses a debit of funds from a deposit account (directdeposit.debit).

Final transaction type.

State of associated direct deposit record: REVERSED

Possibly included objects: gpa, direct_deposit, user.metadata

directdeposit.debit.pending.reversal

Reverses a pending debit of funds from a deposit account (directdeposit.debit.pending).

Final transaction type.

State of associated direct deposit record: REVERSED

Possibly included objects: gpa, direct_deposit, user.metadata

fee.charge

Fee assessed to a user.

Final transaction type.

Possibly completed by: fee.charge.reversal

Possibly included objects: gpa, gpa_order, fee_transfer

fee.charge.pending

Authorization with an associated fee.

Temporary transaction type.

Possibly completed by: fee.charge.reversal, fee.charge

Possibly included objects: gpa, gpa_order, fee_transfer

fee.charge.reversal

Reverses a transaction and its associated fee (fee.charge).

Possibly included objects: gpa, gpa_order, fee_transfer

gpa.credit

ACH deposit into a user’s GPA.

Final transaction type.

Possibly included objects: gpa, gpa_order

gpa.credit.authorization

Just-in-Time (JIT) Funding authorization for crediting funds to a user’s GPA (gpa.credit).

Temporary transaction type.

Possibly completed by: gpa.credit.pending.reversal, gpa.credit

Possibly included objects: gpa, gpa_order

gpa.credit.authorization.reversal

Reverses a JIT Funding authorization for crediting funds to a user’s GPA (gpa.credit.authorization).

Final transaction type.

Possibly included objects: gpa, gpa_order

gpa.credit.issueroperator

Admin function for crediting funds to any GPA . Functionally the same as gpa.credit.

Possibly included objects: gpa, gpa_order

gpa.credit.networkload

Loads funds through a card network service, such as Visa ReadyLink or Mastercard RePower, at a participating merchant location.

Final transaction type.

Possibly included objects: gpa

gpa.credit.networkload.reversal

Cancels the full amount of a load performed through a card network service (gpa.credit.networkload), such as Visa ReadyLink or Mastercard RePower. Permitted only on the same day as the load.

Final transaction type.

Possibly included objects: gpa

gpa.credit.pending

Pending ACH deposit into a user’s GPA.

Temporary transaction type.

Possibly completed by: gpa.credit.pending.reversal, gpa.credit

Possibly included objects: gpa, gpa_order

gpa.credit.pending.reversal

Reverses a pending ACH deposit into a user’s GPA (gpa.credit.pending).

Final transaction type.

Possibly included objects: gpa, gpa_order

gpa.credit.reversal

Reverses an ACH deposit into a user’s GPA (gpa.credit).

Final transaction type.

Possibly included objects: gpa, gpa_order

gpa.debit

Debits funds from a user’s GPA back into a funding source.

Possibly included objects: gpa

gpa.debit.issueroperator

Admin function to debit funds from any GPA. Functionally the same as gpa.debit.

Possibly included objects: gpa, gpa_order

gpa.debit.reversal

Reverses a debiting of funds from a user’s GPA back into a funding source (gpa.debit), thereby moving funds from the funding source back into the GPA.

Final transaction type.

Possibly included objects: gpa_order

original.credit.authorization

Original credit transaction (OCT) authorization for crediting funds to a GPA.

Temporary transaction type.

Ledger impact: Positive.

Possibly included objects: original.credit.authorization.reversal, original.credit.authorization.clearing

original.credit.authorization.reversal

Reverses the financial impact of an OCT authorization (original.credit.authorization).

Final transaction type.

Ledger impact: Negative.

original.credit.authorization.clearing

Completes an OCT authorization (original.credit.authorization).

Final transaction type.

Ledger impact: Positive.

original.credit.auth_plus_capture

Single-message OCT for crediting funds to a GPA.

Ledger impact: Positive.

original.credit.auth_plus_capture.reversal

Reverses the financial impact of a single-message OCT (original.credit.auth_plus_capture).

Ledger impact: Negative.

pindebit

PIN-debit transaction at a point-of-sale terminal.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.atm.withdrawal

Withdraws cash at an ATM.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.authorization

PIN-debit authorization at an automated fuel dispenser (AFD).

Temporary transaction type.

Possibly completed by: pindebit.authorization.clearing, pindebit.authorization.reversal

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.authorization.clearing

Completes a PIN-debit authorization at an AFD (pindebit.authorization).

Final transaction type.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.authorization.reversal

Reverses the financial impact of a PIN-debit authorization at an AFD (pindebit.authorization) when zero dollar PIN debit reversal is enabled.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.authorization.reversal.issuerexpiration

Authorization drop initiated by Marqeta due to elapsed time. Most transactions of this type originate from authorizations at AFDs.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.balanceinquiry

Balance inquiry via the card network e.g., at an ATM.

Non-financial transaction.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.cashback

PIN-debit transaction for cash back requested at a point-of-sale terminal.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.chargeback

Marqeta-initiated PIN-debit chargeback.

Possible states: INITIATED, PREARBITRATION, ARBITRATION, CASE_WON

Ledger impact: Positive if credit_user is true; none if credit_user is false.

Possibly completed by: pindebit.chargeback.reversal, pindebit.chargeback.completed

Possibly included objects: gpa, chargeback, user.metadata

pindebit.chargeback.completed

Completes a PIN-debit chargeback initiated by Marqeta (pindebit.chargeback).

Possible states: CASE_WON

Ledger impact: Positive.

Possibly included objects: gpa, chargeback, user.metadata

pindebit.chargeback.provisional.credit

Provides a credit by moving a PIN-debit chargeback (pindebit.chargeback) from the workflow for non-provisional credit to provisional credit.

Final transaction type. Requires settlement.

Possibly included objects: gpa, chargeback, user.metadata

pindebit.chargeback.provisional.debit

Removes the initial credit by moving a PIN-debit chargeback (pindebit.chargeback) from the workflow for provisional credit to non-provisional credit.

Final transaction type. Requires settlement.

Possibly included objects: gpa, chargeback, user.metadata

pindebit.chargeback.reversal

Reverses a rejected, Marqeta-initiated, PIN-debit chargeback (pindebit.chargeback).

Possible states: CASE_LOST, NETWORK_REJECTED

Ledger impact: Negative if credit_user is true; none if credit_user is false.

Possibly included objects: gpa, chargeback, user.metadata

pindebit.chargeback.writeoff

Writes off the PIN-debit chargeback (pindebit.chargeback) and credits the account holder while Marqeta or its customer absorbs the cost.

Final transaction type.

Possible states: WRITTEN_OFF_PROGRAM, WRITTEN_OFF_ISSUER

Ledger impact: Positive.

Possibly included objects: gpa, chargeback, user.metadata

pindebit.credit.adjustment

Adjusts the amount of a PIN-debit cashback (pindebit.cashback) or PIN-debit withdrawal (pindebit.atm.withdrawal) for non-AFD transactions without a preceding event.

Final transaction type.

Possibly included objects: card_acceptor, gpa, gpa_order

pindebit.quasicash

PIN-debit transaction at a point-of-sale terminal for items equivalent to cash, such as traveler’s checks, money orders, foreign currency, or gaming chips.

pindebit.refund

Refunds a PIN-debit transaction (pindebit).

Possibly included objects: card_acceptor, gpa

pindebit.refund.reversal

Reverses a PIN-debit transaction refunded at an ATM (pindebit.refund).

Also appears as refund.authorization.reversal.

Possibly included objects: card_acceptor, gpa, merchant, gpa_order_unload, user, card

pindebit.representment

Merchant dispute of a Marqeta-initiated chargeback (authorization.clearing.chargeback).

Possible states: REPRESENTMENT

Ledger impact: Negative if credit_user is true; none if credit_user is false and representment amount equals original amount; positive if credit_user is false and representment amount is less than original amount.

Possibly included objects: gpa, chargeback, user.metadata

pindebit.reversal

Reverses the financial impact of a PIN-debit transaction (pindebit) or PIN-debit authorization (pindebit.authorization) when zero dollar PIN debit reversal is not enabled.

Possibly included objects: card_acceptor, gpa, user.metadata

pindebit.transfer

ATM transfer between a checking and a savings account.

programreserve.credit

Credits funds to a program reserve account.

programreserve.debit

Debits funds from a program reserve account.

pushtocard.pending

The state of a Push-to-Card transaction until a response (success or failure) has been received and the state changes to pushtocard.debit.

pushtocard.debit

Debits funds from a Push-to-Card payment card.

pushtocard.reversal

Reverses a debit of funds from a Push-to-Card payment card (pushtocard.debit).

refund

Refunds a cardholder’s transaction.

Possibly included objects: card_acceptor, gpa

refund.authorization

Authorization for a purchase return.

Temporary transaction type.

Possibly completed by: refund.authorization.reversal, refund.authorization.clearing

refund.authorization.clearing

Completes a purchase return authorization (refund.authorization).

refund.authorization.reversal

Reverses a purchase return authorization (refund.authorization).

token.activation-request

Request to activate a digital wallet token.

transaction.unknown

Helps to identify transaction errors. Unlikely to occur.

transfer.peer

Moves money between GPAs. Results from sending a request to the /peertransfers endpoint.

Possibly included objects: gpa, peer_transfer

transfer.program

Movement of funds from the cardholder’s GPA to the program funding source. Results from using the /programtransfers endpoint.

Possibly included objects: gpa, programtransfers

The following is a sample transaction notification. The type and amount fields are always returned. Other fields and object groups are conditionally returned. Refer to the preceding table for a list of objects possibly included for each transaction type.

Copied

Is this helpful?

Yes
No
Possible values for cardholder_presence field
Code Description

0

Cardholder not present

1

Cardholder present

Possible values for card_presence field
Code Description

0

Card not present

1

Card present

For more information about the transactions object, see Transactions.

Feedback on this page?

If you feel we can do anything better, please let our team know.