From a click to a customer.
Find the connections that contribute to verified revenue.
Know what brought them here.
A click is a beginning. A payment tells you more. Connect both, then keep the record clear when a customer renews or a payment is refunded.
- Signed Stripe payment events
- Server-verified customer identity
- Partial refunds without double counting
Little details.
A bigger difference.
LinkRunway connects an eligible click to a server-identified customer, then attributes verified payments using your selected model. Stripe webhooks or a trusted backend can supply payment and refund events.
Identify customers on your server
Use a stable customer ID when reporting a signup. Keep names and email addresses out of URL parameters and public share links.
Report the payment once
Send a purchase or subscription event with a unique event ID and an amount in the currency’s smallest unit. The server key keeps client devices from inventing revenue.
Close the loop
Send refunds against the original event. Review net revenue and partner earnings alongside the campaign that acquired the customer.
The journey has a return.
Follow an illustrative payment from discovery to reconciliation.
A connection begins.
An eligible campaign click creates a signed attribution token.
Good questions.
Clear answers.
How is Stripe revenue verified?
The receiver checks the Stripe signature against the exact raw request body. Accepted live-mode events enter a durable queue. Test deliveries are validated separately and never added to revenue.
What if Stripe delivers the same payment more than once?
Provider deliveries are deduplicated, and the PaymentIntent ID identifies the revenue event. Repeated deliveries cannot create another payment or commission.
Can refunds arrive before their payments?
Yes. The reconciliation worker retries a refund until its original payment is available. Partial refunds cannot exceed the remaining payment balance.