Overview
When a Gift Transaction (GT) is scheduled for a future start date in Payments2Us, the system creates an initial Authorization (AUTH) transaction with an Unpaid status. When the first recurring payment is processed, a second GT is created with a Paid status.
Use Case / Scenario
- A recurring gift is scheduled to start in the future.
- Payments2Us creates an AUTH GT record (Unpaid, Banked Payment = No) at import.
- When the first payment runs, a new Paid GT is created.
- The initial Unpaid AUTH GT remains in the database, which can affect reporting if included.
How the “Gift Transaction” Process Works with NPC
- An AUTH GT is created for future commitments before any payment is processed.
- It remains Unpaid, with “Banked Payment” set to No.
- The first actual payment generates a Paid GT.
- The AUTH GT is not updated to Paid; it serves as a historical authorization.
- Reports and processes should exclude Unpaid AUTH GTs to avoid discrepancies.
Relevant Questions This Article Covers
- Why is a GT created for future start dates even before payment?
- Why does the first GT remain Unpaid while subsequent GTs are Paid?
- How should GT reporting handle Unpaid AUTH transactions?