Testing payment integrations
Keep sandbox and production revenue separate, then follow the checks for your payment provider.
Talivia does not have a Live / Test switch. The credential connected to a website determines which provider environment Talivia calls and where it provisions the managed webhook.
Keep the data separate. Use one Talivia website for staging or sandbox payments and another for production. This keeps test revenue out of production conversion and attribution reports.
Use two websites
| Talivia website | Tracked experience | Provider credential | Data it should contain |
|---|---|---|---|
| Product — Sandbox | Staging site or test checkout | Test or sandbox key/token | Test payments only |
| Product | Production site and checkout | Live or production key/token | Real customer payments only |
The provider environment is only a connection detail. Talivia verifies and processes every supported event delivered by that connection; it does not classify, hide, or filter revenue by a separate payment mode.
Shared test flow
- Create the sandbox Talivia website and install the tracker on the staging experience.
- Connect the provider's test credential in Website settings → Revenue.
- Complete checkout from a tracked browser session.
- Confirm the payment amount, currency, status, and provider.
- Confirm the payment is matched to the expected session and traffic source.
- Follow the provider guide for refunds, subscriptions, delivery logs, and provider-specific errors.
When the flow is verified, connect the live credential to the production Talivia website. Keep the sandbox website for later integration changes.