Record the session before Payment API checkout
Talivia stores the first referrer, campaign values, landing page, visitor identity, and the product activity that happened on your website.
Payment attribution API
Payment attribution API for every paid session
Send completed payments through one backend endpoint and connect custom checkout, bank transfers, crypto processors, app stores, or invoices with the Talivia session that created them.
Payment matched
Payment APIPayment provider
$149.00Paid
This payment was attributed to a customer from google.com who landed on /pricing
- Source
google.com
- Landing page
- /pricing
- Checkout data
- sessionId
High confidence
How the integration works
How Payment attribution API works in Talivia
Your server sends a payment only after the money is confirmed. Include the Talivia session ID for an exact journey match, plus stable customer fields so later payments can reconnect.
Talivia keeps the payment event as the source of truth for revenue and the website session as the source of acquisition context. When the available identifiers agree, the payment inherits its referrer, campaign, landing page, visitor, and first-touch or last-touch attribution fields.
Supported checkout paths
Payment API revenue attribution for the checkout you already use
Choose the path your customers already follow. Talivia uses the strongest supported session signal available for that flow, without forcing you to replace the provider or move checkout onto a new page.
Checkout preview
TPro planBilled monthly$149.00
Total due$149.00
Secure checkout powered by Payment APICustom checkout configuration
Send the current Talivia session to your backend before the order is created.
Payment confirmedPayment API sends Talivia this session after a successful checkout.
Attribution method
From Payment API checkout to an attributed revenue record
A completed payment becomes useful marketing data only after its provider identity is joined with the browser session. Talivia records that relationship as one inspectable attribution record instead of hiding the match inside a conversion total.
Payment detailsMatched
$149.00Paid
ProviderPayment API
Paid atMay 12, 2024 · 18:57
Customeralex@company.com
Attributed sessionFirst touch · high confidencegoogle.com/pricing
Google searchSource recorded
Viewed /pricingLanding page
Started checkoutSession attached
Payment received$149.00
Receive a verified Payment API payment
The backend api supplies the payment status, amount, currency, checkout identity, customer identity, and supported subscription or refund events.
Reconcile the two records
Talivia uses sessionId, return-page data, or the strongest supported fallback to connect the payment with a session and report the match confidence.
Revenue reporting
See Payment API revenue by source, campaign, and landing page
Attributed Payment API payments appear beside the website dimensions you already use to understand traffic. Compare referrers, channels, campaigns, keywords, and landing pages by revenue, then expand a row to inspect the latest payment behind it.
The payment record keeps the amount, provider, payment status, acquisition source, landing page, and match confidence together. That makes aggregate reporting useful without losing the ability to investigate an individual customer journey.
Open the Payment API setup guideRevenue by sourceLast 7 days
ReferrersCampaignsLanding pages
SourceVisitorsPaymentsRevenue
Payments after checkout
Recurring revenue, refunds, and Payment API attribution gaps
Revenue attribution does not stop at the first successful checkout. Talivia keeps later payment events attached to the strongest known customer relationship and leaves unmatched revenue visible when that relationship is missing.
Revenue activityPayment API payments and attribution status3 payments
PaymentWhat Talivia keepsStatus
$149.00Server-side
Never expose the payment key in browser code
AttributedGoogle · /pricingThe Talivia API key stays on your backend and the payment is sent only after your system verifies the money.
$149.00Idempotent
Retry without counting revenue twice
RenewalOriginal source keptA stable transaction ID identifies the payment when your backend repeats a delivery attempt.
$89.00Flexible matching
Start with the exact session, keep customer fallbacks
Needs reviewNo session signalsessionId provides the strongest match, while provider customer IDs, external IDs, and email hashes can reconnect later payments.
Payment API revenue attribution questions
Practical answers about connecting Payment API payments with website sessions, checkout signals, subscriptions, and refunds.
What is the Talivia Payment API?
It is a backend endpoint for recording confirmed revenue from a custom or unsupported payment system and matching it with Talivia traffic.
Which payment systems can use the API?
Any backend that can confirm a completed payment can send it, including custom checkout, bank transfers, crypto processors, app stores, and invoice systems.
How is a custom payment matched to a visitor?
Pass window.talivia.getSessionId() to your backend before checkout and include that sessionId in the confirmed payment request.
Can I safely retry a payment request?
Yes. Reuse the same unique transactionId when retrying so the request updates the existing payment instead of creating a duplicate.
Payment attribution API
Follow the next Payment API payment back to its traffic source
Connect one website, complete a test payment, and verify the source, landing page, and paid session in Talivia.