Reseller billing and limits

How to recover a paid proxy order with missing GB

TL;DR

Find the paid Checkout Session, match it to the offer, then read the purchase row and its saved provider operation. If the provider already applied the grant, finish that purchase. If the outcome is uncertain, keep the original operation open before issuing any more GB.

In this guide

Match the receipt to the order your shop sold

Ask for the shop order reference, the amount and currency, and the approximate payment time. In your own Stripe account, locate the Checkout Session for that order. Check its current payment status against the customer account, plan, quantity and price in your sales record. A customer screenshot helps locate the purchase. The merchant records establish what to deliver.

The published starter verifies the webhook signature and requires payment_status to be paid. A delayed payment can complete checkout while money is still pending. The starter later handles checkout.session.async_payment_succeeded. Your shop must add its own check that the paid amount matches the purchased tier. If payment and order disagree, keep the allowance on hold until the discrepancy is explained.

Read the purchase and its provider operation together

Look up the purchase by stripe_session_id. The same session can receive several event IDs, sometimes out of order. The starter records delivery_state and saves operation_token before sending a mint or top-up. Use that saved token for a read-only lookup. A webhook HTTP status on its own cannot tell you whether a customer key exists.

What the operator should do with each reading
What you seeNext action
Paid, no purchase rowCheck the signed event’s delivery and its customer and tier mapping. The starter can acknowledge an event with missing metadata without granting access. Reconcile the sale against the original session before sending it through fulfillment.
Pending, provider outcome uncertainKeep the original token and check the same operation again. A timeout can happen after the provider applied the grant.
Provider reports applied, shop still pendingContinue the original purchase. The starter reads the affected key and completes the local record. A second mint or top-up would add another allowance.
Provider reports retryable or rejectedA retryable refusal can run again under the same token. A confirmed rejection closes that token without an effect. The starter records a new attempt for the same purchase.
Delivered, customer still cannot connectCheck the linked key’s remaining allowance, expiry and holds. Keep the purchase delivered while diagnosing access.

One 3 GB order with two payment notices

Suppose an existing customer bought a 3 GB top-up for a key capped at 5 GB. At 09:10 the completed-session notice arrives while payment is pending. At 09:16 a delayed success confirms payment. The provider raises the cap to 8 GB, but the shop loses the response. At 09:18 the success notice arrives again.

The operator matches both notices to the same Checkout Session. The purchase is pending and its saved operation reports applied. The starter recovers the key and completes that purchase. The customer has one paid 3 GB increase. A second top-up would produce an incorrect 11 GB cap. These figures are lifetime limits. To explain what the customer can use now, subtract usage from the cap in the plan’s unit.

Close the case with a delivery record

Record the order reference, paid amount and currency, purchased GB, key management ID, provider outcome, and time fulfillment was confirmed. Show the customer their order and updated allowance in the signed-in shop. Keep webhook payloads, passwords and provider operation tokens out of customer messages.

A manual hold can keep a topped-up key offline. If the customer instead questions how much they have already used, compare two dated counter readings for that key. The white-label program guide explains who handles the customer’s refund or dispute. The starter has no scheduled worker that resolves old pending purchases once Stripe retries end. Give each outstanding paid order an owner and a time for its next review.

Common questions

Does a successful webhook response prove my customer received the GB?
Look up the purchase by Checkout Session and confirm its delivery state and customer key. An ignored event, an unpaid completion or a duplicate can also receive a successful HTTP response.
What if two different paid orders arrive for the same customer?
Keep both session IDs. The starter lets one purchase for the customer finish before dispatching the next. That avoids minting two first keys while preserving both legitimate orders.

Sources