Docs/Paddle

Paddle integration setup

Use a signed Paddle notification destination to send payment and subscription events into Metrivo. Status becomes active only after a valid webhook is received.

Capability: signed attribution and lifecycle support, plus independent Revenue Assurance reconciliation using a permission-scoped Paddle API key validated for read access.

Read-only webhook flow

Metrivo does not need charge-capable Paddle credentials. Save the webhook endpoint secret in Data Connections; it is encrypted before storage.

Setup steps

1. Open Metrivo Data Connections and generate the Paddle webhook URL.
2. In Paddle, create a notification destination and paste the URL.
3. Select these events: transaction.completed, transaction.billed, transaction.payment_failed, subscription.activated, subscription.created, subscription.past_due.
4. Copy the endpoint secret from Paddle and save it in Metrivo.
5. Send a simulated or test transaction webhook. Metrivo marks the provider active only after signature verification succeeds.

Metadata for attribution

Pass Metrivo visitor/session identifiers in Paddle custom data before checkout. Without these fields, Metrivo may fall back to customer email or leave revenue unattributed.

// Client: send this object to your checkout endpoint
const metadata = window.Metrivo.getAttributionMetadata()

// Server: include it in Paddle custom_data
await createPaddleCheckout({
  items: [{ price_id: "pri_123", quantity: 1 }],
  customer: { email: "customer@example.com" },
  custom_data: {
    ...metadata,
    plan: "growth"
  }
})