Connect a payment provider
A step-by-step setup for verified payment ingestion.
On this page
1. Choose your provider
Open Integrations for the correct site. Find the provider in the complete directory. Connection forms specify that provider's required fields; not every provider uses the same API key or webhook mechanism.
2. Supply credentials securely
Create the necessary credential in your provider account and enter it in Weeveo's connection dialog. Keep provider credentials server-side. Weeveo stores integration secrets encrypted; they are inputs, not values returned by list_integrations. Do not put them in the browser tracker or public docs.
3. Configure the webhook
Copy the exact webhook URL shown by Weeveo. If automatic registration is supported, use that action. Otherwise configure it in the provider dashboard with the required event selection and signing secret. Providers with unsigned notification pointers are verified by fetching the payment from the provider API instead.
4. Verify a payment
Use the provider's supported test workflow, then inspect webhook status and Revenue. Match live/test modes and credentials. A successful connection test proves the supplied credential works; it does not prove that your provider has delivered a new payment event.
5. Import history when supported
Use Sync only for providers that advertise history synchronization. The API exposes a bounded import limit. Review sync errors and date coverage before comparing imported revenue with all-time provider totals.
6. Disconnect or rotate
Disconnect from the selected site when no longer needed. Rotate compromised provider credentials at the provider too. Disconnecting stops the configured connection; it is not a request to erase all previously ingested analytics.
Troubleshooting
Check webhook delivery logs, the exact canonical HTTPS callback URL, signature secret, account environment, selected site and event status. Reconciliation jobs must run for delayed/self-healing processing. list_webhook_events returns sanitized audit status without raw payment payloads.
Still looking for an answer? Try troubleshooting or get in touch.