When discussing a payment issue, name the event, the identifier and the system that owns the record.
Collections and payouts describe direction
A collection is an incoming payment to a business; a payout is an outgoing payment to a recipient. The same business may use both for one customer relationship. For example, it might collect an order payment and later initiate an approved outgoing payment. Calling everything a transaction is convenient, but direction helps finance teams understand what they are investigating.
A payment method is not a checkout page
UPI is a payment system. A payment gateway provides the technology through which payment requests and results are handled. Hosted checkout is an interface customers visit to pay, while a payment link is a shareable entry point into a payment request. These concepts can work together: a customer can open a link, reach a hosted page and select UPI.
Status, settlement and reconciliation differ
Payment status describes the state of a particular payment. Settlement concerns the transfer of funds between the relevant participants or accounts. Reconciliation compares your records with provider or bank records and explains differences. A successful payment therefore does not answer every accounting question, and a settlement total may cover more than one payment.
Use precise identifiers
An order ID belongs to your business record. A provider payment ID identifies the payment in the provider system. A bank reference helps investigate the relevant bank transfer. RBI describes the RTGS UTR as a 22-character transaction reference; do not assume every payment rail uses that same format. Preserve the identifier exactly as returned rather than creating a visually similar substitute.
Connect the vocabulary to implementation
An API lets your software request an operation or retrieve information. A webhook sends an event notification back to your system. An idempotency key helps identify repeated submissions of the same instruction according to a provider’s contract. Use the glossary below the blog library as a quick reference, then read the relevant ZytePe integration guide for field names, authentication and supported behaviour.
Sources & further reading
Industry references support the concepts above. ZytePe capabilities and integration details are described in the linked product documentation.