To ensure a scalable, consistent, and maintainable webhook architecture, SoFi Tech Solutions standardized templates and delivery settings for the Events API.
The scope and triggers for the events are unchanged; only the fields returned in the request body have changed. If your events were set up before standard templates, some fields you receive today have a different name in the standard template. The value is the same; only the field name changes.
Policy changes and timeline
Effective October 6, 2026, SoFi Tech Solutions will enforce a standardized template policy for the Events API. Our public API documentation reflects the standard templates.
-
Existing integrations: Your current template configurations will continue to function and receive events exactly as they do today. However, these custom configurations are now frozen and can no longer be edited.
-
Modification requests: If you request to modify an existing event (such as adding or renaming a field), you will first be required to migrate to the standard template.
To update your integration, find each field name in the Field mapping table below and update your code to read the new name instead. Fields that aren't listed keep their legacy name.
Standardized delivery
When migrating to a standard template or enabling a new event, your webhook-receiving endpoint must adhere to the standardized delivery logic. See Paths and Content Types for details.
Payload examples
For example, a BAUT: auth event you receive today might include:
{
"pmt_ref_no": "999101003022",
"timestamp": "2025-01-31 17:20:33 MST",
"account_id": "20211"
}
With the standard template, the exact same values arrive under the new names:
{
"prn": "999101003022",
"event_ts": "2025-01-31 17:20:33 MST",
"balance_id": "20211"
}
Field name mapping
Each field below has the same new field name on every event where it appears.
Note
This page lists global renames that apply across all programs. If your events include custom fields that were set up only for your program, contact your SoFi Tech Solutions representative to get a mapping of your specific templates.
| Legacy field name | New field name |
|---|---|
account_id | balance_id |
balance | available_balance |
billing_amt | billing_amount |
card_id | cad |
case_no | claim_id |
cur_code, currency | currency_code |
effective_dt | effective_ach_dt |
fund_pmt_ref_no | fund_prn |
local_amount, local_amt | local_currency_amount |
local_currency, local_curr_code | local_currency_code |
merch_loc | merchant_location |
merch_name | merchant_name |
merch_num | merchant_number |
od_open_to_buy | available_overdraft_balance |
old_status | previous_account_status |
open_to_buy | available_balance |
opentobuy_ts | available_balance_ts |
pmt_ref_no | prn |
response_code | auth_response_code |
rules_denied | rules_results |
settle_currency | settle_currency_code |
sign_amount | amount_sign |
timestamp | event_ts |
tran_timestamp | event_ts |

