Delinquency Events

The following are events triggered by activities related to automated delinquency management of secured credit cards. These are sent to you in the Account Events Webhook which is part of the Events API.

payment_reminder_event

The number of days before a payment due date for a credit account. This event is triggered two times per billing cycle:

X days before the due date (where X is the value configured during setup of your delinquency management program system).
1 day before the due date.

Code — N/A
Event trigger — An upcoming payment due date configured on a credit account.
Processes — These processes contain the event trigger:
- An internal process that determines there is an upcoming payment due date on a credit account.

Field	Type	Description
`prn`	string	Galileo 12-digit payment reference number (PRN) for the account. Example: `"999101003022"`
`due_date`	string	Due date of the payment for the billing cycle. Example: `"2025-03-17"`
`final_balance`	number	For credit accounts, the final statement balance at the end of a billing cycle. Example: 50
`amount_past_due`	number	Total amount that is past the payment due date, including fees. Example: 25
`amount_paid`	number	The total amount paid towards the billing cycle. Example: 25
`payment_status`	string	The status of the payment. Possible values: `"UNPAID"` `"PAST_DUE"` `"PAID"` `"ZERO_BALANCE"` Example:`"PAST_DUE"`
`late_fee_date`	string	The date a late fee will be assessed if the billing cycle is not fully paid. Example: `"2025-03-20"`
`late_fee_amount`	number	The fee amount that will be assessed if the payment is not received by the specified `late_fee_date`. Example: 5
`delinquency_date`	string	The date the credit account will become delinquent if payment is not made. Example: `"2025-03-25"`
`reason`	string	The reminder for the upcoming due date payment.

# payment_reminder_event.v1 example
{
  "detail": {
    "data": {
      "payment_reminder_event.v1": {
        "prn": "593101003071",
        "due_date": "2025-10-02",
        "final_balance": 50,
        "amount_past_due": 0,
        "amount_paid": 0,
        "payment_status": "UNPAID",
        "late_fee_date": 2025-10-15,
        "late_fee_amount": 10,
        "delinquency_date": "2025-10-31",
        "reason": "FIRST Payment reminder: Payment is due on 2025-10-02. Late fee amount: 10 may be assessed if not paid by 2025-10-15.",
      }
    },
    "metadata": {
      "detail_id": "550e8400-e29b-41d4-a716-446655440000",
      "detail_timestamp": "2025-10-23T14:30:00.123Z"
    }
  }
}

Payment reminder reasons

The values for reason in the payment_reminder_event.v1 are dynamic and based on your configuration of the delinquency management system

First payment reminder:

"FIRST Payment reminder: Payment is due on [due_date]. Late fee amount: [late_fee_amount] may be assessed if not paid by [late_fee_date]."

Second payment reminder:

"SECOND Payment reminder: Payment is due on [due_date]. Late fee amount: [late_fee_amount] may be assessed if not paid by [late_fee_date]."

past_due_payment_status_event

A credit account has an outstanding balance that remains unpaid after the due date for a given billing cycle.

Code — N/A
Event trigger — The account has missed its due date
Processes — These processes contain the event trigger:
- An internal process checks if the payment status for a billing cycle is past due

Field	Type	Description
prn	string	Galileo 12-digit payment reference number (PRN) for the account. Example: `"999101003022"`
due_date	string	Due date of the payment for the billing cycle. Example: `"2025-03-17"`
final_balance	number	For credit accounts, the final statement balance at the end of a billing cycle. Example: 50
amount_paid	number	The total amount paid towards the billing cycle. Example: 25
amount_past_due	number	Total amount that is past the payment due date, including fees. Example: 25
payment_status	string	The status of the payment. Possible values: `"UNPAID"` `"PAST_DUE"` `"PAID"` `"ZERO_BALANCE" Example:`"PAST_DUE"`
late_fee_date	string	The date a late fee will be assessed if the billing cycle is not fully paid. Example:`"2025-03-20"`
delinquency_date	string	The date the credit account will become delinquent if payment is not made. Example: `"2025-03-25"`
reason	string	The reminder for the current payment status.

# past_due_payment_status_event.v1 example
{
  "detail": {
    "data": {
      "past_due_payment_status_event.v1": {
        "prn": "593101003071",
        "final_balance": 50,
        "due_date": "2025-09-30",
        "amount_past_due": 50,
        "amount_paid": 0,
        "payment_status": "PAST_DUE",
	  		"late_fee_date": "2025-10-15"
        "late_fee_amount": 10,
        "delinquency_date": "2025-10-31",
        "reason": "The payment status was changed to PAST_DUE due to non-receipt of the minimum required payment by the due date 2025-09-30. Late fee amount: 10 may be assessed if not paid by 2025-10-15.",
      }
    },
    "metadata": {
      "detail_id": "550e8400-e29b-41d4-a716-446655440000",
      "detail_timestamp": "2025-10-22T14:30:00.123Z"
    }
  }
}

Past due status reasons

The values for reason in the payment_reminder_event.v1 are dynamic and based on your configuration of the delinquency management system.

"The payment status was changed to [payment_status] due to non-receipt of the minimum required payment by the due date [delinquency_date]. Late fee amount: [late_fee_amount] may be assessed if not paid by [delinquency_date]."