Quickstart
Go from zero to a working payment in under 10 minutes with a single API call. Start here.
Paymee uses a hosted checkout model. Your server creates a payment session, you redirect the buyer to the Paymee-hosted payment page, and we notify your server of the outcome with a signed webhook. Your servers never touch card data.
sequenceDiagram
participant S as Your server
participant P as Paymee
participant B as Buyer
S->>P: POST /sessions/
P-->>S: { checkout_url }
S->>B: redirect to checkout_url
B->>P: buyer pays (3-D Secure)
P-->>S: webhook session.* (X-Paymee-Signature)
P->>B: redirect to return_url
Quickstart
Go from zero to a working payment in under 10 minutes with a single API call. Start here.
Hosted checkout
The full create-session → redirect → result lifecycle. Read the guide.
Webhooks
Receive session.succeeded / session.failed events and verify the
X-Paymee-Signature. Set up webhooks.
API Reference
Every endpoint, generated from our OpenAPI specification. Browse the reference.
You need two credentials from your Paymee merchant dashboard — they are different and used in different places:
| Credential | Looks like | Used for |
|---|---|---|
| Secret API key | sk_live_… / sk_test_… |
Authenticating your API requests (Authorization header) |
| Webhook secret | whsec_… |
Verifying the signature on incoming webhooks |
Use the sk_test_… key against the sandbox while building,
then swap to sk_live_… to go live.
Building with an AI assistant? Every page has Copy for LLM and Download .md buttons under its title, and the whole site is available as plain Markdown for LLM context: