#### PLT-002 | Payment gateway integration **Source:** p.5–6, p.14–15, p.25, p.124–126 · **Actor:** trainee, independent trainer, system - An electronic payment gateway collects: a trainee's **course enrollment**, a trainee's **package purchase**, and an independent trainer's **package (subscription)**. The client contracts the gateway provider (DEC-06). - Covers: creating the payment · tracking its status (**Pending / Paid / Failed**) · linking it to the enrollment or subscription · tracking revenue · basic payment reports. - **Never** used for hall bookings, events, or the hall commission — those happen outside the platform. - Rules: repeated taps must not create duplicate payments; a successful payment is never changed manually; cashback held for a failed payment returns to available (TRN-010). **Acceptance, rules and screen notes citing PLT-002:** - WF-01 — Trainee enrollment and payment — Browse / search → course details → enrollment review (offer, cashback, points) → payment → success: seat counted, My courses, trainer entitlement (commission), cashback, ticket (in-person) — TRN-007, TRN-008, TRN-010, TRN-011, TRN-012, TRN-024, PLT-002 - BR-ENR-03 — A payment is always linked to its enrollment or subscription; repeated taps never create a second payment; a successful payment is never edited manually. — TRN-011, PLT-002, ADM-035