Integrations
Connect Dodo Payments revenue
Verify Dodo Payments revenue, refunds and disputes for one Premely site.
- Dodo Payments
What it is
The Dodo Payments connection adds supported payments, refunds and dispute outcomes to the selected site's revenue. Premely checks the provider's signature before accepting an event.
Why use it
Use it when Dodo Payments is the source of truth for payments, refunds and dispute outcomes.
Before you start
- You need owner or admin access in the Premely workspace.
- You need permission to create a webhook in Dodo Payments.
- Choose Test or Live to match the Dodo Payments environment you are connecting.
How to use it
- 1
Reserve the Premely webhook URL
Open your site's Settings, choose Integrations, find Dodo Payments and choose Connect. Choose Test for Dodo Test Mode or Live for Live Mode and select Create Dodo Payments endpoint. Copy Webhook URL and keep the Premely dialog open. The reserved endpoint cannot verify events until you add Dodo's signing secret.
Reserve the Premely URL, configure the endpoint in Dodo Payments, then paste Dodo's signing secret back into Premely. Shown in Premely with disposable demo data; your values will differ.
- 2
Create the Dodo Payments webhook
In Dodo Payments, check the mode at the bottom of the sidebar. Open Developer, then Webhooks. On Endpoints, choose Add endpoint. Leave Integration set to Custom webhook, paste the reserved Premely URL into Endpoint URL and optionally enter Premely revenue as the description.
In Dodo Payments, open Developer, Webhooks, then Add endpoint. Paste the URL reserved by Premely into Endpoint URL. The field is empty here to keep account-specific URLs private.
Dodo Payments test dashboard · Captured 2026-08-27
- 3
Select supported events
Under Subscribed events, search for
payment.succeededand tick its checkbox. Replace the search text and repeat forrefund.succeeded,dispute.openedanddispute.won. Confirm the form says Filtering to 4 event type(s), leave Enabled on, then choose Create endpoint. An empty event selection sends every event type.
Search for payment.succeeded and tick its checkbox. Repeat for refund.succeeded, dispute.opened and dispute.won. The screenshot demonstrates the first selection; your final count should be four.
Dodo Payments test dashboard · Captured 2026-08-27
- 4
Copy the signing secret from Dodo
Open the saved endpoint and stay on Overview. In Signing secret, use the copy icon at the right of the masked value. Do not choose Rotate secret. This secret belongs to the endpoint you just created; it is not a Dodo API key.
In the endpoint Overview, use the copy icon at the right of Signing secret. Keep the value private. You do not need to reveal or rotate it to connect Premely.
Dodo Payments test dashboard · Captured 2026-08-27
- 5
Activate the connection in Premely
Return to the open Dodo Payments dialog in Premely. Paste the copied value into Provider signing secret and choose Activate Dodo Payments revenue. Keep the signing secret private and never put it in a website script.
Paste Dodo's endpoint secret into Provider signing secret, then choose Activate Dodo Payments revenue. The example secret is masked. Captured from the real Premely interface using disposable local-review values. Example URLs and credentials cannot be used for a real connection.
- 6
Send a test event from Dodo
For a Test connection, open the endpoint's Testing tab. Choose
payment.succeededin Select an event type, then choose Send example. Check Message attempts for a successful response. Do not send example payments to a Live connection.
On the endpoint's Testing tab, choose payment.succeeded from Select an event type. Send example becomes available after an event is selected. Use a Test connection for this check.
Dodo Payments test dashboard · Captured 2026-08-27
- 7
Verify the first event
Reopen Dodo Payments in Premely and check Last verified event. It must show a timestamp instead of Waiting for first event. If delivery succeeded but that field is still waiting, the event may not contain a supported payment: check any displayed error and verify with a completed payment from the same Dodo test environment. Live revenue starts after a supported live event arrives.
Connected means the endpoint is configured, not that a payment has arrived. After a supported event, Last verified event must change from Waiting for first event to a timestamp. This example has not received an event. Captured from the real Premely interface using disposable local-review values. Example URLs and credentials cannot be used for a real connection.
What to expect
Check the site and environment
Each connection sends revenue to one Premely site. A Test connection does not verify a Live connection. Keep the provider environment and the Premely mode the same throughout setup.
Currencies stay separate
Premely does not silently combine or convert different currencies. Provider revenue appears in Revenue and Revenue / Visitor only in its valid currency context.
Revenue and visitor attribution are separate
A verified payment can appear in revenue without being linked to a visitor. Premely shows the visitor link only when the payment carries matching Premely attribution data.
Duplicate deliveries do not duplicate revenue
If the provider retries the same event, Premely does not count it as another payment.
Disputes do not inflate revenue
Premely records supported dispute outcomes with their correct economic direction rather than counting them as new payments.
Useful ways to apply this
Payment lifecycle reporting
Review successful Dodo Payments transactions, supported refunds and disputes beside the selected site's analytics.