← Partners overview
Partners · technical integration

Wire your affiliate webhook to Panya.

This page is the technical spec your affiliate-program operator or IT team needs. It assumes the relationship is already agreed; if you are evaluating Panya, start at /partners.

The model

Flat-fee affiliate, no pay-to-rank

Panya is a peptide vendor matchmaker. We score every vendor against a public 11-signal rubric and route users based on fit, not payment. Vendors that meet the routable threshold (70 of 100) appear in match results; vendors above it pay the same flat affiliate commission per confirmed conversion. No tier, no boost, no auction.

Disclosure is on every match page. Users know the link is affiliate-tagged before they click.

The flow

How a conversion gets attributed

  1. 1. User clicks a Panya match link. Every outbound on Panya goes through panya.health/api/v/[your-vendor-id]?s=[submission-id]. We log the click + redirect to your URL with utm_content=[submission-id] appended. You receive standard UTM tags as the visitor.
  2. 2. User completes a purchase on your site. Standard checkout. The submission ID rides along in your URL params and lands in your order metadata, however you pass it through (cookie, hidden field, sub-id parameter in your affiliate platform).
  3. 3. Your affiliate platform fires a webhook. When the conversion is confirmed (paid, not refunded during the chargeback window), the platform POSTs to:
    POST https://panya.health/api/affiliate/webhook?provider=[provider]
    Where [provider] is one of: refersion, impact, everflow, generic.
  4. 4. Panya credits the referrer + emits a receipt. The conversion lands in our affiliate_revenue table. If the original click carried a referral code (a Panya user who shared the link), the credit ledger vests an earn for that user. Reconciliation happens monthly.
Supported platforms

What we accept and how

Refersion

Set the conversion webhook URL in Refersion to https://panya.health/api/affiliate/webhook?provider=refersion. We verify via X-RFC-Signature HMAC-SHA256 of the raw body using a shared secret you email to partner@panya.health. Pass the Panya submission ID in sub_id so we can stitch the conversion back to the original click.

Impact

Configure a postback in Impact pointing at https://panya.health/api/affiliate/webhook?provider=impact. Authentication uses the SID + AuthToken HTTP Basic pair Impact issues. Pass the Panya submission ID in SubId1.

Everflow

Webhook URL https://panya.health/api/affiliate/webhook?provider=everflow. Everflow does not sign payloads, so we verify via IP allowlist; email partner@panya.health with the source IPs your Everflow instance posts from. Pass the submission ID in sub1.

Generic / custom

If you run an in-house affiliate stack or a platform not listed above, use https://panya.health/api/affiliate/webhook?provider=generic. Send a JSON POST body with vendor_id, order_id, order_total, commission_total, currency, submission_id fields. Authentication via x-panya-secret header matching a shared secret. Email partner@panya.health to provision.

Sample payload

Generic provider example

POST https://panya.health/api/affiliate/webhook?provider=generic
Content-Type: application/json
x-panya-secret: <your-shared-secret>

{
  "vendor_id": "your-vendor-slug",
  "order_id": "ORD-2026-12345",
  "order_total": 320.00,
  "commission_total": 32.00,
  "currency": "USD",
  "submission_id": "9c9e1e0e-...-...-...",
  "occurred_at": "2026-04-29T14:32:00Z"
}

We respond 200 OK with the affiliate_revenue row id on success. 401 on bad signature, 409 if the order_id is already on file (idempotent retries are safe).

Test before going live

The two-conversion handshake

Before flipping production traffic, we recommend a two-conversion test:

  1. 1. Send a test conversion with order_total = 0.01 and order_id = "PANYA-TEST-1". We confirm receipt via partner@panya.health.
  2. 2. Send a real conversion from a known Panya match (we coordinate the submission ID in advance). We confirm the row appears in affiliate_revenue and the credit ledger emits as expected.
  3. 3. Flip production. Once both test conversions reconcile cleanly, the integration is live.
Reporting

What you receive back

Monthly reconciliation email to your partner-program contact. Itemised list of conversions Panya recognised against your platform's reporting. Discrepancies flagged in the same email so we can chase down attribution gaps before they compound.

Payment runs on net-30 from your platform's payout date. Standard ACH, wire, or PayPal Business; no Stripe-side integration needed because Panya is the affiliate, not the merchant.

Ready to wire it up?

Email partner@panya.health with your platform choice, the IP range or signing-key method you need, and a contact for the test handshake. Typical turnaround from agreed deal to live conversion path is 3 to 5 business days.