payductor / orchestration
Orchestrate payments. Move faster.
Create payment links, launch hosted checkout and connect server-side payment events through one operational layer.
Operational loop
- CREATEPayment links, hosted checkout, API
Open a session from the dashboard or your server.
- CONNECTCredentials and signed webhooks
Store keys on your server. Receive HMAC events when status changes.
- OBSERVETransactions and status changes
Filter, search, and follow a payment through the workspace.
- SETTLETerms in the merchant agreement
Settlement state is visible after go-live — not a public timetable.
Methods
Major cards and selected digital wallets. Availability depends on merchant profile and the current programme.
Talk to the API, then ship
REST create, list, and status. Secrets stay on the server. Live keys are issued after KYB, from the dashboard.
POST /api/v1/payment/create
X-API-Key: <server-only>
X-API-Secret: <server-only>
{ "amount": 99.99, "currency": "USD", "title": "Order" }View APIoperators
One layer for the people who automate
Payment links for the rest of the team. API and webhooks for the systems that already run your stack.
- Dashboard links without a build
- Server-side create session
- Signed webhook delivery
settlement
State you can operate on
After a successful payment, funds move according to the merchant agreement. The workspace shows settlement state for live activity.
- Captured
- In settlement
- Settled
controls
Keys, KYB, processors
KYB before live processing. Third-party processors handle card data. API credentials stay in the merchant dashboard, on your server — not in this website.
Security overview- KYB before activation
- HMAC-signed webhooks
- Server-only API secrets
Partners introduce. We review.
Bring merchants. We assess fit, run KYB, and go live. Economics stay in the agent workspace.
Stand up the payment layer
Apply with the business. We will say if we can support it.