Payment connectors

How it works

Pick your payment provider under Settings → Revenue and paste a restricted API key (with read-only access plus permission to create a webhook — never full account access). ShonyLabs calls that provider's own API to register a webhook automatically, so there's nothing to configure on the provider's side yourself. Every recorded purchase or refund flows into the same revenue analytics as the Transactions API.

Linking a sale back to a visitor

A payment processor has no idea which website visitor made a purchase — that link only exists in your own checkout flow. Whichever provider you connect, pass the visitor's ShonyLabs ID (window.shonylabs.visitorId) through at checkout time, or the purchase won't be attributed to any traffic source:

Stripe

Pass it as client_reference_id (or metadata.shonylabs_visitor_id) when creating the Checkout Session.

Polar

Pass metadata.shonylabs_visitor_id when creating the Checkout via the Polar API.

Lemon Squeezy

Pass checkout.custom.shonylabs_visitor_id when creating the checkout via the Lemon Squeezy API or checkout overlay options.

Paddle

Pass customData: { shonylabs_visitor_id: window.shonylabs.visitorId } when opening Paddle Checkout.

Shopify

Add a cart/order note attribute named shonylabs_visitor_id(e.g. a hidden field in a cart script) so it appears in the order's note_attributes.

DodoPayments, or anything else not listed

There's no ShonyLabs-specific integration for DodoPayments or other processors not listed above. Instead, call ShonyLabs' own Payments API directly from your backend — typically from that provider's own webhook handler, right after a successful payment. It works identically regardless of which processor you use.