This website
The route simulator runs in your browser. It does not connect to a payment API, request wallet access, collect private keys or create accounts. Sample exports are generated locally.
The inquiry form prepares text locally. You decide whether to open an email app and send it. This site does not accept KYC documents. Fonts and brand assets are served with the website; no advertising or analytics scripts are included in this build.
Separate payment services
The existing payment portal has a different operational scope. Its identity verification, account access, financial data and provider integrations are governed by that portal’s applicable arrangements. This marketing website’s local-only simulator is not evidence of the portal’s security controls.
Controls required for a production integration
A production deployment requires appropriate authentication, access control, isolated customer contexts, protected provider credentials, validated callbacks, transaction idempotency, audit trails and operational incident handling.
These are integration requirements, not a claim that this website has independently certified their implementation in every service. No SOC 2, ISO 27001, PCI certification or external penetration-test result is claimed here.
Report a security concern
Email [email protected] with “Security report — Swyby” in the subject. Include the affected URL, a non-sensitive description and safe reproduction steps. Do not email secrets, customer records or proof that requires accessing another person’s account.
We do not publish a guaranteed response time or bug-bounty reward on this page.