Revenue
Payment Events API
Send authenticated server-side payment and refund evidence to Premely.
Setup availableAlready connected? This opens your existing setup.
New to Premely? Log in or sign up to continue.
What it does
The Payment Events API lets a server-side payment system append payments, refunds, disputes, dispute reversals and corrections to the canonical Premely revenue ledger when a native provider connection is not the right fit.
A custom checkout
Record a completed server-confirmed payment after the payment provider reports the final outcome to your backend.
A finance correction
Append a refund, dispute or correction event so reports reflect the commercial event without rewriting the original payment.
Before you connect
Use a secure server environment. Never send a workspace API token from browser code or publish it in a client application.
Create a workspace token with only the revenue:write scope and identify the Premely site that should receive the event.
Good to know
Revenue entries are immutable
Accepted payment events append to the revenue ledger. Send a refund, dispute reversal or correction event when a later business event changes the revenue story.
Currencies remain separate
Premely does not silently combine currencies. Send each event in its actual currency and review reporting in the relevant currency context.
Customer identity is not accepted
Do not send raw visitor or customer identifiers. Payment event attribution accepts an optional Premely attribution hash instead.
Set it up, step by step
Follow the complete Payment Events API guide, including configuration, verification and troubleshooting.
