A core account is now participating in overdraft, or a core account has opted back in to overdraft. For more information see Creating an Overdraft Account.
- Code —
ODIN
- Event trigger — Account feature 17 changes to
P
(participating).
The core account is created in a participating state because ODOPT is set.
An overdraft account is created with ODOPT set.
The core account opts in to overdraft after previously opting out of an existing overdraft account. - Processes — These processes contain the event trigger:
- Program API endpoints:
- Create Account for the core account with ODOPT set.
- Set Account Feature with
featureType: 17
andfeatureValue: P
. - Add Account for the overdraft account with ODOPT set.
- Customer Service Tool
- Galileo-hosted cardholder website
- Program API endpoints:
Fields
All fields are strings. Your field names may vary. Default fields are included in the default webhook template. See Default and optional fields for more information.
Field | Default | Description |
---|---|---|
balance_id | X | The balance ID, also called the |
ch_group_id | Corporate Hierarchy group identifier. Example: |
|
msg_event_id | Unique Galileo-generated identifier for this message. Example: |
|
msg_id | The four-letter code to identify this event. Example: |
|
pmt_ref_no | X | Galileo 12-digit payment reference number (PRN) for the account. Example: |
prod_id | X | The product ID of the account. Example: |
prog_id | X | The program ID of the account. Example: |
timestamp | X | Date-time when this event was created in Mountain Standard Time (GMT -0700). Format: |
type | X | The name of this event: |
Example
# overdraft_opt_in example:
{
"balance_id": "20211",
"ch_group_id": "2544",
"msg_event_id": "243693",
"msg_id": "ODIN",
"pmt_ref_no": "999101003022",
"prod_id": "1701",
"prog_id": "305",
"timestamp": "2025-01-31 17:20:33 MST",
"type": "overdraft_opt_in"
}