Glossary

Glossary

Term	Meaning
Adapter	code that understands one provider's formats: detection, normalization, decoding, correlation
Manifest	an adapter's public description of what it supports and its limitations
Record	one parsed unit of input (one JSON object, one line, one form body, one HTTP message)
Normalized event	a provider-neutral description of something that happened, keeping the provider's own status
Stage	the kind of operation: payment, authorization, capture, refund, dispute, payout, subscription, ...
Outcome	success, failure, pending or unknown
Decoded error	a provider code with category, retry guidance, next step, confidence and documentation link
Correlation group	events linked by explicit identifiers into one transaction
Delivery key	what identifies a repeated delivery of the same notification (an event id or documented fields)
Finding	the result of a diagnostic rule, with evidence and limitations
Rule catalog version	version of the rule set used for an analysis
Authorization	the issuer reserves funds; nothing is collected yet
Capture	collecting an authorized amount; not the same as settlement
Settlement	funds actually moved between institutions
Rebill	a recurring charge in a subscription
Chargeback	a dispute raised through the card scheme by the cardholder's bank
Payout	money sent to a customer, for example a gaming withdrawal
Postback	a provider's server-to-server notification, often form-encoded or in a URL
PPLsynth	the marker used in every synthetic identifier in fixtures and examples
HR-1, HR-2, HR-3	the waves in which high-risk providers are added