A PIN change was successfully staged. Event code ADPS is for attempts made using the direct POST PIN-set procedure, and AFPS is for attempts made using the direct render PIN-set procedure. When the PIN has successfully changed, the PNCH: system_pin_change event is sent. See the PIN-Set Procedures guide for more information.

Codes — ADPS, AFPS
Event trigger — Staging a PIN change is successful.
Process — This process contains the event trigger:
- Galileo receives a PIN-set form via direct POST or direct render.

Fields

All fields are strings. Your field names may vary.

Field	Required	Description
balance_id	X	The balance ID, also called the `galileo_account_number`. Example: `"20211"`
code	X	This field is present in the event message only if the PIN set change attempt was made using the Direct POST method, which corresponds with the `ADPS` event code. Successful staging always returns `"0"`.
msg_event_id	X	Unique Galileo-generated identifier for this message. Example: `"243693"`
msg_id		The four-letter code to identify this event. Example: `"AFPS"`
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"`
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: `"agserv_PIN_change_success"`

Example

# agserv_PIN_change_success example:
{
  "balance_id": "20211",
  "code": "0",
  "msg_event_id": "243693",
  "msg_id": "AFPS",
  "pmt_ref_no": "155101003022",
  "prod_id": "1701",
  "prog_id": "305",
  "timestamp": "2023-01-29 17:20:33 MST",
  "type": "agserv_PIN_change_success"
}