how it works

This page explains the high-level Billz Pro execution workflow. Sensitive implementation details are intentionally omitted.

Two execution modes (high-level)

A) Direct conversion execution

Use crypto directly to fund a fiat payment execution.

B) Collateralized liquidity execution (lending/borrowing-based)

Use crypto as collateral to access liquidity, then route that liquidity toward fiat payment execution.

Availability depends on configuration, jurisdiction, risk policy, and supported workflows.

Workflow (visual)

Standard execution flow

1

Initiate payment

You provide:

• recipient name

• bank details (IBAN for SEPA / routing+account for ACH)

• fiat amount (EUR or USD)

• reference / memo (recommended when supported)

• optional internal reconciliation metadata (invoice ID, vendor tag)

2

Select funding approach

Depending on workflow and configuration:

• direct crypto-funded execution, or

• collateralized liquidity route (lending/borrowing-based)

3

Compliance and operational checks

Billz Pro may apply:

• KYC / KYB / EDD review (when required)

• risk thresholds

• jurisdiction checks

• rail constraints / cutoffs

4

Conversion / liquidity orchestration

Billz Pro orchestrates the required steps to prepare fiat execution.

5

Fiat execution (SEPA / ACH)

A fiat transfer is initiated on:

• SEPA (EUR)

• ACH (USD)

6

Proof & confirmation

Billz Pro generates structured artifacts to support accounting and audit workflows.

Indicative timelines (not guaranteed)

Rail	Typical range (indicative)
SEPA	Same day / next business day (cutoff dependent)
ACH	1-3 business days (rail dependent)

Timelines are not guaranteed and may be affected by banking cutoffs, compliance review, and operational conditions.

Mini FAQ

Are timelines guaranteed?

No. Banking cutoffs, compliance review, and operational conditions can affect timelines.

Does collateralized mode remove liquidation risk?

No. It introduces collateral management and liquidation risk that must be monitored.

Can Billz Pro share the exact routing logic publicly?

No. Public docs intentionally avoid disclosing sensitive execution details.