SwybyBUSINESSDiscuss your route

Trust starts with clear responsibilities.

The software layer and the regulated payment layer have different jobs. They must stay visible before, during and after every route.

Operator
Swyby, Inc.
Scope
B2B software
Status
Provider-led services

Who is responsible

ResponsibilitySwyby softwareRegulated provider
Customer onboardingCollect or relay information; present the provider’s onboarding flow.Set requirements, verify customers and decide eligibility.
Funds & private keysNo customer-funds wallet or omnibus account in this model.Designate funding accounts or wallets; control custody where applicable.
Conversion & pricingPresent provider figures and separately disclosed platform fees.Supply the quote, exchange assets and execute settlement.
AML & sanctionsSupport required data handoff and escalation; do not override a refusal.Perform required checks, review alerts, block or reject where required.
Status & recordsOrganize provider events, show unresolved states and export workflow records.Provide authoritative payment status, settlement records and case decisions.
SupportHelp with software, integration and routing questions; coordinate provider cases.Investigate held funds, returns and regulated-service complaints.

Funds and control

The Swyby.pro model does not use a Swyby-owned omnibus account or wallet to collect or pool customer payment funds. A customer funds the account or wallet designated for that customer’s approved provider arrangement.

Swyby is not the customer’s custodian, does not control customer private keys and does not execute conversion from its own inventory. Operational configuration and provider permissions must preserve those boundaries.

A disclosed customer, every time

Each business and relevant beneficial owners are disclosed as required by the provider. Separate customer environments and provider references support isolation and traceability. No “one approval covers everyone” promise is made.

Providers set their KYC, KYB, AML, sanctions and transaction-monitoring requirements. Travel Rule information is collected and transferred where applicable. Beneficiary checks depend on the provider, destination and transaction type; not every beneficiary requires an identical onboarding process.

Transparent commercial arrangements

Swyby may charge agreed software or platform fees. A provider may collect and remit an agreed partner fee where the contract permits. These arrangements must be disclosed clearly and kept distinct from provider conversion rates, network costs and payout fees.

No public price, guaranteed spread, minimum commitment or provider commission schedule is offered on this site.

Approval has a defined scope

Company KYB approval, acceptance of a business model, an executed contract, production access and availability of a particular route are separate milestones. One does not prove the others.

A provider’s commercial acceptance is not a legal opinion that Swyby is exempt from every licensing or regulatory requirement. Launch decisions must be assessed against the actual activities, contracts, jurisdictions and control of funds.

When a route stops

Swyby handles software questions and helps coordinate a provider case. Decisions about compliance holds, release of funds, settlement or refunds remain with the responsible provider. Support response time does not guarantee a funds-release time.

Read security and support