A card-load request was approved. Available balance has changed.

Code — AAPM
Event trigger — You or Galileo approve a request to load funds onto a card.
Process — This process contains the event trigger:
- Galileo receives an authorization request for a card load from a card network.

Fields

The data elements (DEs) indicated in the field descriptions may vary by network. All fields are strings. Your field names may vary.

Field	Required	Description
act_type	X	See Activity Type for possible values. Example: `"VI"`
amount	X	The amount of the authorization request. Includes fees and upcharges. DE004 times the conversion rate in DE009. The amount is signed: `-` to debit the account and `+` to credit the account. Example: `"10.25"`
auth_id	X	Galileo-generated ID for the authorization request. This ID is unique per subnetwork. Example: `"12303090"`
auth_tran_type		Based on DE003, processing code. Type of authorization request. See Authorization types for possible values. Example: `"5"`
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"`
cad	X	Galileo-generated card ID. Example: `"12534"`
credit_balance		For credit accounts, the total amount of unpaid purchases and advances. Example: `"325.00"`
currency		Currency code for `amount`, which is the currency of the cardholder account.. Example: `"840"`
local_surcharge_amt	X	The surcharge amount (DE028) added by the merchant or ATM operator. This amount is included in `amount`. Example: `"2.50"`
mcc	X	Merchant category code (DE018). Example: `"5712"`
merchant_location	X	Merchant city and state (from remaining part of ISO DE043). Example: `"NEW YORK, NY"`
merchant_name	X	Merchant name (first 22 characters of DE043). Should not be used for matching; instead, use `merchant_number`. Example: `"Widgets Incorporated"`
merchant_number	X	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: `"AAPM"`
network	X	See Events Network Codes for possible values. Example: `"V"`
open_to_buy	X	The available balance to spend. Example: `"500.00"`
original_auth_id	X	The ID of a prior authorization in the sequence. For example, for a completion, this is the `auth_id` of the preauthorization. For a reversal, this is the `auth_id` of the transaction that is being reversed. Example: `"12303085"`
otype	X	See Transaction Types for possible values. Example: `"W"`
pmt_ref_no	X	Galileo 12-digit payment reference number (PRN) for the account. Example: `"155101003022"`
prod_id	X	The product ID of the account. Example: `"1701"`
prog_id	X	The program ID of the account. Example: `"305"`
response_code	X	See Authorization Response Codes for possible values. Example: `"05"`
timestamp	X	Date-time when this event was created in Mountain Standard Time (GMT -0700). Format: `YYYY-MM-DD hh:mm:ss MST` Example: `"2023-01-29 17:20:33 MST"`
type	X	The name of this event: `"auth_payment"`

Example

# auth_payment example:
{
  "act_type": "VI",
  "amount": "10.25",
  "auth_id": "12303090",
  "auth_tran_type": "5",
  "avail_cash": "143.11",
  "avail_credit": "432.00",
  "balance_id": "20211",
  "cad": "12534",
  "credit_balance": "325.00",
  "currency": "840",
  "local_surcharge_amt": "2.50",
  "mcc": "5712",
  "merchant_location": "NEW YORK, NY",
  "merchant_name": "Widgets Incorporated",
  "merchant_number": "L4DIV6D5LM4X7LF",
  "msg_event_id": "243693",
  "msg_id": "AAPM",
  "network": "V",
  "open_to_buy": "500.00",
  "original_auth_id": "12303085",
  "otype": "W",
  "pmt_ref_no": "155101003022",
  "prod_id": "1701",
  "prog_id": "305",
  "response_code": "05",
  "timestamp": "2023-01-29 17:20:33 MST",
  "type": "auth_payment"
}