Introduction
This documentation describes how to integrate Kollect from your backend systems using the server-to-server (S2S) API to create payment links, and how to receive signed webhooks when payments complete or fail.
Who this documentation is for
The intended audience is backend engineers, technical leads, and integration partners who need to:
Issue invoice-backed payment sessions without driving the flow from a browser-only SDK session.
Automate order fulfillment when a customer pays on the hosted Kollect payment experience.
Verify webhook authenticity using a shared signing secret.
If you are building a browser or mobile client with user sessions, additional product surfaces (for example DPoP-protected status polling) may apply; this guide focuses on API key + HMAC server flows.
What you can build
Create payment URL
POST /sdk/server/create-payment returns a paymentUrl, paymentId, and invoice identifiers.
Hosted checkout
Your customer opens the URL and completes payment in the Kollect UI.
Outbound webhooks
Kollect POSTs JSON to your HTTPS endpoint with X-Kollect-Signature when the payment settles (for kollect-server integrations).
Documentation map
End-to-end sequence and component boundaries.
Prerequisites, onboarding, and configuration checklist.
Endpoint contracts, headers, and examples.
Credentials, signing, and idempotency.
When events fire, how to register URLs, and how to verify signatures.
Statuses, errors, and rate limits.
Lifecycle, testing, and operational best practices.
Quick links
Primary endpoint: Create payment URL
Webhook verification: Payload & signature verification
Errors: Error handling
Versioning note
Behavior documented here reflects the Kollect backend implementation (routes, middleware, and services). Always confirm base URLs, credentials, and environment-specific settings with your Kollect platform or integration contact for production deployments.
Last updated
Was this helpful?