LoveGoBuy payments: check what changed before paying again

When a LoveGoBuy payment appears delayed, first identify what you were paying for and what each screen actually says. A product order, a balance top-up and a parcel payment are different transactions. A provider's pending entry is not automatically evidence that the platform credited the intended action.

Keep the transaction and purpose together

Record the amount, currency, time and intended purpose privately. Compare the transaction reference with the relevant order or balance event rather than matching on the amount alone.

If you were buying an item from a saved link, keep the selected variant with that record. For example, the LoveGoBuy tracksuit product page helps identify the intended product; it is not a receipt and does not confirm a successful payment.

Understand the provider's wording

PayPal's help article about pending orders distinguishes an authorization from the seller collecting the payment. In that order flow, a pending authorization can remain before capture; a completed payment indicates collection. This is a PayPal-specific distinction, not a definition of every LoveGoBuy status or confirmation that the method is available in your checkout.

For any provider, inspect the transaction details before interpreting a bank notification as the final result. Do not transfer a status definition from one payment method to another.

Avoid an accidental second transaction

Before retrying, check whether there is already a pending or completed entry and whether the intended order or balance changed. If the screens disagree, preserve their timestamps and ask which transaction is associated with the action.

A useful support request says what you attempted, what the provider shows and what the platform shows. Send only the identifiers needed through the appropriate private channel. Never send passwords, verification codes or full card details.

Compare currencies and totals carefully

A displayed product price, checkout total and account debit can refer to different stages or currencies. Compare like-for-like values before concluding there is an error. Read any exchange or fee information presented during your actual transaction; do not apply a fee percentage quoted for someone else's payment.

For freight, keep the payment linked to the parcel selection described in the shipping guide, not merely to the original product order.

Follow a refund as its own event

A return request is not proof that a refund was approved, and an approved request is not proof that funds reached the intended destination. Keep the request, approval and payment record distinct.

Check the stated destination of the funds and the actual transaction status rather than assuming that all refunds follow the same route. The returns guide helps organise the questions about the item; payment evidence answers a separate question about the money.

When a payment does not complete

Compare the platform's order state with the payment provider's state before trying again. Keep the amount, currency, time and reference for the attempt. A pending authorisation, a decline and a completed charge require different follow-up; an error screen alone does not tell you which occurred.

If the provider shows a charge but the order has not updated, send the order reference and transaction details through the platform's support channel. Do not send passwords or full card numbers. For a refund, track the approved amount, destination and actual receipt separately.