Overdraft Workflows

Authorization with overdraft

This flowchart illustrates authorization and settlement for a card transaction that uses overdraft funds.

  1. An account holder makes a purchase over card network rails and the card network sends an authorization request. The DDA has insufficient funds to cover the purchase, but the account is linked to an overdraft account.
  2. Galileo determines whether the authorization request is eligible to draw from the overdraft account. Eligibility depends on whether the transaction is a qualifying purchase and if there are sufficient funds available in the overdraft account line of credit.
    • Not eligible — Galileo denies the authorization request and sends response code 51 to the card network.
    • Eligible — Galileo places a hold for the authorized amount on the overdraft account.
  3. The card network sends a settlement batch file.
  4. Galileo backs out the authorization hold on the primary account and posts the overdraft funds to the primary account, bringing the DDA balance to 0.00.
  5. Galileo sends the SETL: setl event.

Overdraft fees

An overdraft fee is usually charged when a primary account draws from its overdraft account, with some exceptions. This flowchart illustrates the process to determine when overdraft fees are charged to an account.

  1. An account holder makes a purchase with insufficient funds in the primary account. The DDA draws on its overdraft account.
  2. Galileo determines if the amount owed to the overdraft account exceeds the de minimis threshold.
    • Does not exceed — Galileo does not post an overdraft fee.
    • Exceeds — Galileo determines whether the fee would exceed the fee cap:
  3. If the overdraft amount is paid within the grace period, Galileo reverses the overdraft fee and sends the FREV: fee_reversal event message.



Overdraft fees do not trigger repayment. The DDA balance will remain negative until the overdraft amount is paid.

Overdraft repayment

This flowchart illustrates the process to repay funds owed on an overdraft account.

  1. A payment is made to a DDA that is linked to an overdraft account. Galileo sends the BPMT: pmt event.
  2. If funds are not owed on the overdraft account, the full payment is posted to the DDA balance after any fees are paid.
  3. If funds are owed on the overdraft account once settlement occurs:
    a. The payment is first posted to the overdraft balance.
    b. The remaining amount is posted to the DDA after any fees are paid.


When an overdraft account remains unpaid for a specified period (usually 35 days), a process to transfer funds and charge-off the account is triggered. This flowchart illustrates a possible configuration for the charge-off process.

  1. An overdraft account remains unpaid for the number of days set by ODPDN (typically 35 days).
  2. The owed funds are moved out of the overdraft account and into the DDA. The total amount owed is now the negative primary account balance combined with the overdraft line of credit consumed (configured with ODPAA).
  3. The primary account and overdraft account are set to status: R (charge-off) (configured with ODMOB).
  4. Account feature 17 (overdraft eligibility or participation) is set to I (ineligible). The account holder can no longer use the overdraft account (configured with ODOBI).
  5. Galileo sends the ODOT: overdraft_opt_out event.