Event
payment.plan_created
Sent only from:
- Unified tokenized flows when a
paymentorpayment planis setup, with a tokenized payment process. - USAePay payment processing when a
planorpaymentis set up.
event, eventCategory, organization, optional agent, timestamp, and payload — the object below is the payload value.
Treat tokenized as sensitive (processor payment key / token). Use HTTPS, protect your signing secret, and avoid logging full bodies.
How payload is built
Cora merges normalized fields with plan-specific data. Optional passthrough when present: consumerId, currency, externalId, accountId, gateway, outcome.
Normalized and plan fields (inner payload)
| Field | Description |
|---|---|
title | "<Organization name> Payment Plan Created" |
name | Customer / payor name when provided |
fileNumber | Account / file reference uploaded with |
balance | Balance string when provided |
callId | Voice / session id when provided (e.g. metadata runId) |
tokenized | Processor token / payment key when provided |
paymentType | Instrument hint: card, ach, or wallet (voice flows default to card) |
totalAmount | Sum of scheduled payment amounts (string, two decimals) |
paymentDate | First scheduled payment date (YYYY-MM-DD) |
numberOfInstallments | Length of the payments array |
amountPerInstallment | Configured per-installment amount string |
downPayment | Down payment from plan config (0.00 when none) |
regularity | weekly, biweekly, monthly, or one_time |
planType | One of: settle_today, settlement_plan, regular_payment_plan, single_payment |
payments | Array of { paymentDate, amount, processed } — processed is true only for the first row when an immediate charge succeeded (e.g. tokenized paymentToday or USAePay plan success) |
phoneNumber | Phone when provided |
agentName | Agent display name when provided |