An Odoo payment gateway is ready for launch when the provider’s transaction and the corresponding Odoo record agree across successful, failed, cancelled and interrupted journeys. A successful checkout screen alone is not enough. Use this checklist in a test environment before accepting real orders.

Confirm the exact installation

Record your Odoo version, hosting model, company, website and connector release. Check the module’s stated compatibility before installing it. A module for one major Odoo version should not be assumed to work unchanged on another.

Waslio’s marketplace listings are Checkout.com for Odoo 18 and Noon Payments for Odoo 19. Check the selected version and current listing details before purchase. These are separate provider integrations, not a claim that every payment method or feature is available in both.

Keep a short acceptance sheet: scenario, expected result, provider reference, Odoo reference, actual result and reviewer. Use test identities and amounts.

Separate test configuration from production

Odoo documents a Test mode for payment providers. Use the selected provider’s corresponding sandbox credentials and supported test scenarios. A demo provider can illustrate Odoo’s payment flow, but does not prove a third-party connector works. See Odoo’s online payments documentation.

Check that callback URLs point to the intended environment and are reachable. Keep credentials in the server configuration, outside screenshots, support tickets and public files. Confirm how your connector authenticates provider notifications and what it records when verification fails.

List supported payment methods, currencies and countries for your merchant account. Availability depends on both the account and the integration; a provider advertising a method does not prove your installed module supports it.

Test the customer journeys

  • Successful payment: confirm amount, currency and transaction reference on both sides.
  • Declined payment: show a useful retry route without treating the order as paid.
  • Customer cancellation: return safely to the order without creating a false success.
  • Authentication challenge: complete and abandon the challenge, where the provider supports that test.
  • Closed browser: close the payment tab before the return page and check eventual status.
  • Repeated button click: check whether multiple attempts are created and whether any duplicate charge is possible.

Write down the expected Odoo state for each case. Order confirmation, payment authorization, captured payment and invoice reconciliation are separate checkpoints; your workflow determines when fulfilment may start.

Check delayed notifications and recovery

A browser redirect and a provider notification can arrive in different orders. Test delayed notifications, repeated notifications and a temporary network failure using the provider’s documented test tools.

The expected outcome is one correctly recorded business result for a successful payment, with a safe way to investigate an unresolved attempt. A repeated event must not trigger another fulfilment or mark a different order paid.

Compare the amount, currency and reference, not only a “success” label. If the provider shows a charge while Odoo still shows pending, investigate the callback and transaction mapping before telling the customer to pay again.

Verify refunds and the first live transaction

If your connector supports refunds, test full and partial refunds separately. Confirm where each refund must be initiated and whether its status is synchronized. If it does not support an action, document the manual process instead of assuming automatic handling.

Payment refunds, credit notes and returned stock should each follow the intended business workflow. Do not infer that a refund automatically restocks an item or completes accounting reconciliation.

Before launch, review the evidence with the person responsible for orders and payments. After switching to production credentials, make one authorized low-value live test if appropriate for your business, verify the transaction and complete the agreed refund or accounting process. Monitor the first real orders closely.

Frequently asked questions

Why does the provider show paid while Odoo shows pending?

A missing or delayed callback, rejected notification or mapping error can cause disagreement. Compare transaction references and inspect the connector’s logs; avoid assuming another payment is required.

Does a sandbox test guarantee production works?

No. Production credentials, account permissions and notification configuration also need verification.

Where can I discuss a Waslio connector?

See the Checkout.com connector or Noon Payments connector, then send your Odoo version and payment workflow. Do not include API keys or card details.