Compare recorded offline payments, hosted online checkout, sandbox testing and live verification.
Different methods carry different evidence#
Only enable methods the business can actually accept and reconcile. A displayed provider name or saved credential is not proof that a payment has settled.
| Choice | When it fits | What it changes |
|---|---|---|
| Cash or recorded bank transfer | Money confirmed through the business’s offline process. | An authorised operator records the receipt. Keep the real payment evidence and reference. |
| Hosted online checkout | A supported provider collects payment securely. | Requires an implemented, verified merchant connection and a matching supported currency. Provider returns alone never mark the invoice paid. |
| External card terminal | A separate terminal takes the payment. | Where offered, the operator records its confirmed reference. This is not an integrated terminal charge. |
Saved, tested and live are different states#
Choose the provider account’s actual country and environment. Store only the requested credential types. Credentials remain masked after saving; never put them in a support message or ordinary notes.
A connection test checks the implemented capability. Live readiness also depends on merchant approval, permissions, account configuration and the supported payment lifecycle. A catalogue-only provider needs an integration request.
Sandbox and live#
Sandbox money cannot settle a real production business invoice. The disposable demo uses sandbox external effects and cannot prove merchant approval. Select the right environment before testing or accepting payments.
If a result is uncertain, reconcile the existing attempt before creating another charge. A credit note or cancellation does not automatically return money through the provider.
Keep the active workspace, actual business requirements and current setup summary in view. A guide explains a choice; it does not make that choice for you.