A transaction to move funds into an account was only partially completed because of load-limit violations. For example, if the limit is $100 and the amount of the deposit is $150, then $100 is posted and $50 is placed in a queue to be posted later. Available balance has changed.

Code — BSPM
Event trigger — Only part of a deposit or payment is posted because of load limit violations.
Processes — These processes contain the event trigger:
- Create Payment endpoint
- Create Account Transfer endpoint
- Customer Service Tool

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
ach_trans_id		Unique Galileo-generated identifier for an ACH transaction. For BADJ and BPMT, this field may contain the `auth_id` of a card-load transaction. Example: `"7971383"`
act_type		For all payments the activity type is `"PM"`.
amount	X	Amount of the transaction. Unsigned. Example: `"63.21"`
avail_cash		For debit accounts, the `open_to_buy` plus available overdraft. Example: `"143.11"`
avail_credit		For credit accounts, the available credit limit to spend. Example: `"432.00"`
balance_id	X	The balance ID, also called the `galileo_account_number`. Example: `"20211"`
ch_group_id		Corporate Hierarchy group identifier. Example: `"2544"`
credit_balance		For credit accounts, the total amount of unpaid purchases and advances. Example: `"325.00"`
description		Description of the payment. Example: `"Transfer from Savings"`
ext_trans_id	X	External transaction ID. Example: `"1234-abcdefg"`
hold_days	X	Number of days that a payment was held before posting. Example: `"1"`
immed_amt	X	The amount of the payment that was posted immediately. Example: `"24.55"`
later_amt	X	The amount of the payment that is posted later. Example: `"18.45"`
merchant_name		Merchant name (first 22 characters of DE043). Should not be used for matching; instead, use `merchant_number`. Example: `"Widgets Incorporated"`
merchant_number		Merchant number (DE042). Example: `"L4DIV6D5LM4X7LF"`
msg_event_id		Unique Galileo-generated identifier for this message. Example: `"243693"`
msg_id		The four-letter code to identify this event. Example: `"BSPM"`
open_to_buy	X	The available balance to spend. Example: `"500.00"`
opentobuy_ts		The exact date-time at which `open_to_buy` was captured. Format: `YYYY-MM-DD hh:mm:ss.ssssss` Example: `"2025-03-17 14:06:50.243654"`
otype	X	See Transaction Types for possible values. Example: `"A"`
pmt_id	X	Galileo-generated identifier for this payment. Example: `"7971383"`
pmt_ref_no	X	Galileo 12-digit payment reference number (PRN) for the account. Example: `"999101003022"`
prod_id	X	The product ID of the account. Example: `"1701"`
prog_id	X	The program ID of the account. Example: `"305"`
source_id		An identifier that maps back to the origin of the adjustment.
timestamp	X	Date-time when this event was created in Mountain Standard Time (GMT -0700). Format: `YYYY-MM-DD hh:mm:ss MST` Example: `"2025-01-31 17:20:33 MST"`
type	X	The name of this event: `"pmt_split"`
user_data		Populated according to your use case and needs by arrangement with Galileo.

Example

# pmt_split example:
{
  "ach_trans_id": "7971383",
  "act_type": "PM",
  "amount": "63.21",
  "avail_cash": "143.11",
  "avail_credit": "432.00",
  "balance_id": "20211",
  "ch_group_id": "2544",
  "credit_balance": "325.00",
  "description": "Transfer from Savings",
  "ext_trans_id": "1234-abcdefg",
  "hold_days": "1",
  "immed_amt": "24.55",
  "later_amt": "18.45",
  "merchant_name": "Widgets Incorporated",
  "merchant_number": "L4DIV6D5LM4X7LF",
  "msg_event_id": "243693",
  "msg_id": "BSPM",
  "open_to_buy": "500.00",
  "opentobuy_ts": "2025-03-17 14:06:50.243654",
  "otype": "A",
  "pmt_id": "7971383",
  "pmt_ref_no": "999101003022",
  "prod_id": "1701",
  "prog_id": "305",
  "timestamp": "2025-01-31 17:20:33 MST",
  "type": "pmt_split"
}