Payductor
Keys, KYB, isolation
Payductor merchant accounts activate after review. The marketing site, the dashboard, and the processing environment are separate.
Account approval and KYB
Live processing starts after KYB on the processing platform. This website does not collect identity documents.
Operational controls
After approval you operate from the dashboard: transactions, links, webhooks, keys, settlement state. We do not publish uptime SLAs, approval rates, or fraud guarantees here.
Data handling
Card data is handled by third-party processors. Intake forms collect business contact fields only and email them to support@payductor.com. No analytics trackers on this site.
API credential handling
Live keys are issued in the merchant dashboard after approval. Store them on your server. Verify HMAC webhooks before you trust an event. Never embed secrets in frontend code.
Dashboard practices
Use Merchant Login only after you have been invited. Named users. Rotate secrets if they leak.
Marketing site versus processing
This site is a public presence. It is isolated from payment APIs, merchant credentials, and internal admin hosts. It does not process payments.
Monitoring and review
Monitoring and sanctions screening sit on the processing platform as part of the operator’s programme — not a licence, not a government endorsement.