Introduction
Once a payment request is created in Lynk, the requested amount is locked. This ensures transparency and prevents disputes after a link has been shared with a student.
If the wrong amount is entered—whether higher or lower than intended—the correction flow depends on whether the payment has already been completed.
If the Payment Is Not Yet Paid
When the request is still Pending:
Do not ask the student to pay using the incorrect link
Simply ignore or let the request expire
Create a new payment request with the correct amount
Share the new link with the student
No further action is required for the incorrect request.
If the Payment Is Already Paid
If the student has already completed the payment:
The original transaction cannot be edited or reversed from the request
Create an adjustment payment request for the difference
Request additional payment if the amount was undercharged
Handle refunds or future adjustments separately if overcharged
Keep communication clear with the student on why the adjustment is needed
This keeps the payment trail accurate and auditable.
Why Requests Can’t Be Edited
Maintains a clear payment record
Avoids post-payment disputes
Ensures gateway and settlement accuracy
Keeps reconciliation clean
Summary
If the wrong amount is requested, the fix depends on payment status. Pending requests can be ignored and recreated, while paid requests require an adjustment request to correct the difference.