Migrating to the Standard Event Templates

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 nameNew field name
account_idbalance_id
balanceavailable_balance
billing_amtbilling_amount
card_idcad
case_noclaim_id
cur_code, currencycurrency_code
effective_dteffective_ach_dt
fund_pmt_ref_nofund_prn
local_amount, local_amtlocal_currency_amount
local_currency, local_curr_codelocal_currency_code
merch_locmerchant_location
merch_namemerchant_name
merch_nummerchant_number
od_open_to_buyavailable_overdraft_balance
old_statusprevious_account_status
open_to_buyavailable_balance
opentobuy_tsavailable_balance_ts
pmt_ref_noprn
response_codeauth_response_code
rules_deniedrules_results
settle_currencysettle_currency_code
sign_amountamount_sign
timestampevent_ts
tran_timestampevent_ts

© SoFi Technology Solutions, LLC 2026    Privacy Disclosure

All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of SoFi Technology Solutions, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of SoFi Technology Solutions, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.