Payment recovery
What happens if Paystack succeeds but PartyDey does not finish the checkout?
A successful provider payment and a completed PartyDey event record are two separate checkpoints. PartyDey includes a recovery flow for cases where Paystack confirms the payment but the browser, redirect, connection, or local synchronization is interrupted before PartyDey finishes the confirmation journey.
Last reviewed: 24 August 2026
The problem recovery is designed for
A guest can successfully complete a Paystack payment and still fail to reach the final PartyDey confirmation screen. The browser may be closed, the network may drop, a redirect may be interrupted, or the PartyDey record may not finish synchronizing immediately.
In that situation, the right question is not whether the guest should pay again. The first step is to verify the original payment reference and determine whether PartyDey already has the corresponding record.
What the PartyDey recovery flow checks
- The event link or slug associated with the original checkout
- The exact Paystack payment reference
- Whether Paystack reports that reference as successful
- Whether PartyDey already has the payment recorded
- Whether the checkout draft contains the event-form data needed to restore the journey
- Whether a missing PartyDey payment record needs to be recreated
Single-payment recovery
For a normal checkout, PartyDey accepts the event reference and Paystack reference, verifies the provider result through the recovery endpoint, and returns the payment record needed to continue to the success flow.
The recovery request uses an idempotency key. Repeating a valid recovery should finalize the existing payment journey rather than intentionally create duplicate payment records.
Group-payment recovery
PartyDey also supports group checkout, where one payer covers multiple beneficiaries. The recovery page has a separate group mode and can use the payment reference together with the group intent identifier when available.
What a guest should do
- Do not immediately make a second payment just because the confirmation page was interrupted.
- Keep the Paystack reference from the successful transaction.
- Use the same PartyDey event link or slug from the original checkout.
- Open PartyDey's payment recovery page and submit the reference in the correct single or group mode.
- If the provider cannot validate the reference or the event context is wrong, contact PartyDey support rather than retrying blindly.
What recovery does not mean
Recovery does not turn a failed or nonexistent transaction into a successful one. The provider reference must verify successfully before PartyDey can restore the corresponding event-payment journey.
It also does not change Paystack settlement timing. Recovery is about synchronizing a successful checkout into the correct PartyDey record and confirmation flow.
Frequently asked questions
Should I pay again if Paystack debited me but PartyDey did not show success?
Not immediately. First use the original Paystack reference with PartyDey payment recovery so the platform can verify whether the successful transaction can be restored to the event record.
What information do I need to recover a PartyDey payment?
For a normal checkout, the PartyDey event link or slug and the Paystack reference are required. Group checkout can also use the group intent ID when available.
Can recovery duplicate my payment record?
The recovery flow uses idempotent handling and checks whether the event already has the payment recorded. Its purpose is to finalize or restore the existing successful journey, not create a second charge.
Does payment recovery work for group payments?
Yes. PartyDey has a separate group confirmation path for one payer covering multiple beneficiaries.
Does recovery guarantee that every reference will succeed?
No. The reference must be valid for the event and must verify successfully with the payment provider. Invalid, failed, or mismatched references cannot be recovered as successful payments.