PARCO BUSINESS · IN DEVELOPMENT

One funding plan.
Many destinations.

Collect, convert and pay across borders. A planned workspace for businesses that pay suppliers, contractors and teams in different currencies.

Fiat + stablecoinsOne or manyAPI + workspace
ILLUSTRATIVE BUSINESS WORKSPACEDraft

Team payout plan

Funding preferenceUSD or USDCSource and payout can differ
AMTeam memberLocal currencyKES
JLContractorApproved walletUSDT
RSSupplierBank transferGBP
Validate → Quote → Approve3 examples

Concept only · No funds or live recipients

THE BUSINESS FEATURE LIST

Every moving part.
One considered flow.

The business release connects funding, conversion, approvals and delivery. Each feature has a visible place in the development plan.

01
Planned

Get paid against a reference.

Accept an identified customer payment for a business, match it to the correct invoice or reference, and manage unmatched funds.

See delivery scope
02
Planned

One list. Many recipients.

Upload a CSV or send a batch by API. Validate each recipient, review their payout method and track each payment separately.

See delivery scope
03
Planned

Fiat in. Crypto to their wallet.

Fund through an approved fiat collection route and deliver USDT or USDC to a verified recipient wallet on an enabled network.

See delivery scope
04
Planned

Prepare, review, approve.

Give teams scoped access, separate preparation from approval, and retain an audit trail for each payment instruction.

See delivery scope
05
Planned

Plan larger conversions.

Request an assisted OTC quote, confirm both settlement legs and track business allocations and treasury movements.

See delivery scope
06
Planned

Build payments into your product.

Connect collections, conversions and payouts through a scoped partner API, with idempotent requests and signed payment updates.

See delivery scope
View all features & phases
INTERNATIONAL TEAM & SUPPLIER PAYMENTS

You fund once.
Each recipient has a route.

A company with fiat or stablecoins can prepare a payment list and choose an available method for each recipient. Full payroll calculations and country-specific employment services are separate scope.

01

Prepare

Add your business funding source and recipient list.

02

Validate

Check identities, details, countries and available methods.

03

Review

Confirm the quotes, fees, allocations and approvals.

04

Deliver

Follow each payout and reconcile the batch.

A PLANNED EXAMPLE

A UK business funds in GBP or USDC. One Kenyan recipient receives KES through an approved local rail; another eligible recipient receives USDT in a verified wallet.

Actual countries, funding accounts, assets and payout methods depend on contracted providers.Explore funding & payout directions
FOR PLATFORMS & PROVIDERS

Your product.
Connected payment rails.

Partners will be able to connect the approved services through an API. The same transaction records and controls will support the workspace and integrations.

Track the partner API
PLANNED INTEGRATION CAPABILITIES
01Scoped access

Keys and permissions for the services you’re approved to use.

02Safe requests

Idempotent payment instructions and clear lifecycle statuses.

03Signed updates

Verified events, retries and reconciliation for exceptions.

BUSINESS, EXPLAINED

Plan with clarity.
Launch with evidence.

Can a company fund in fiat and pay people in crypto?

That is part of the planned fiat-to-crypto route. The company, funding route, conversion counterparty, recipients and wallet networks must be approved. Each recipient’s transfer has its own quote and status.

Can customers pay us in crypto while we settle a business in fiat?

The planned C2B flow identifies the payer, attributes funds to the correct business reference and uses an enabled conversion and settlement route. Unmatched or screened payments enter an exception process before settlement.

Will one batch support different payout preferences?

Yes, that is the product direction. A batch is a list of individually validated transfers, with available currency and method choices. A single recipient failure must not hide the outcomes for the rest of the list.

Are card funding, issued cards and IBANs already included?

No card or account product is enabled today. Card funding, issuing and push-to-card payouts require separate programmes. Named bank accounts or IBANs would also require a contracted account provider; they are not promised by this landing page.

Where can I track the promised features?

The feature map shows core and later-release capabilities, planned phase numbers and outstanding dependencies. It is reviewed product scope; financial features are only marked live once implementation, provider availability and release evidence are verified.