Zoikorum™
Payments & Payouts

Move from funding to professional payout with every step accounted for.

ZoikoRum connects supported payment actions to the engagement state that authorizes them — so buyers can understand funding and release, professionals can understand payout progress, and both sides retain a clear payment record.

See How Payments WorkExplore Payment Protection
A buyer and professional team reviewing an engagement together
Buyer · Payment stateDemo
Payment stateConfirmed
Amount
[Configured from engagement]
Funding state
Confirmed
Release readiness
Blocked · acceptance pending
Last updated
[timestamp]
Shared engagement dependenciesMilestone 2
  • Contract versionCurrent · v4
  • !MilestonePending acceptance
  • ApprovalComplete
  • Hold / disputeClear
Why this state?
Professional · Payout stateDemo
Payout stateNot ready
Payout profile
Complete
Payout state
Waiting on release
Destination
•••• 4021
Last updated
[timestamp]
ConfidenceHow it worksBuyer fundingProfessional payoutDependenciesFees & disclosureRecordsAvailabilityFAQ
Payment confidence

Clear payment state,
on both sides.

A milestone review open on a laptop
01

Connected to the engagement

Payment progression follows the relevant contract, milestone, acceptance, approval, hold and dispute state.

Why this state?
A buyer and a professional each checking status
02

Clear on both sides

Buyers see funding and release status; professionals see payout status — without having to infer one from the other.

See the payout workspace
A payment record open on a laptop
03

A record remains

Material payment events and provider references, where applicable, remain connected to the engagement record.

View Payment Record
Wording

“Payment state” and “payout state” — never “safe” or “guaranteed” without an established mechanism.

Timing

“Estimated” only with a real estimate source; otherwise “timing shown when available.”

Released ≠ received

A release is never presented as the professional having been paid.

Initiated ≠ available

Funding initiated never means funds are available.

How payments & payouts work

Six stages,
two perspectives.

Select a stage to see what the buyer and the professional each experience.

A team celebrating agreement around a table

1. Prepare

Buyer

Review amount, currency and applicable payment terms before committing.

Professional

Complete any payout configuration required for the supported market/program.

Product objectPre-commitment summary
Buyer funding workspace

Amount, state, dependencies —
and one clear next action.

Pick a state. The primary action changes, and duplicate submits are never possible.

Finance Transformation · Example Advisory LLC
Engagement ENG-•••• · last updated [timestamp]
Funded · why?
State
Amount summary
Engagement amount[Authoritative value]
Funded / released / remainingShown when authoritative
Currency[Currency]
Fees / taxIf configured
Funding card
Method[From configuration]
Method statusConfirmed
Applicable termsView terms
Release readiness
  • Contract version
    v4 current
    Valid
  • !
    Milestone acceptance
    Finance Lead
    Pending
  • Approval
    Approval Workflows
    Complete
  • Hold
    Payment Protection
    None
  • Dispute
    Dispute Resolution
    None
Timeline
  1. Funding initiated[time]
  2. Funding confirmed[time]
  3. Release authorizednow
  4. Settlement—
  5. Downstream payout—
Reference bundle
Payment recordPAY-••••-•••
Provider referenceWhere applicable · masked
Contract / milestoneContract v4 · Milestone 2 v2
Release depends on the engagement dependencies.
A buyer checking funding status on her laptop
Idempotent by design

Repeated clicks or retries cannot duplicate money movement. While funding is processing, there is no second submit.

Professional payout workspace

Payout progress, never
inferred from release.

Every blocker names its category, owner and whether you can resolve it.

A professional checking payout progress
No silent payout blockers

If you cannot progress to payout, the UI states the blocker category, who owns the next action, and whether you can resolve it. An indefinite “pending” is never a final state.

Payout · Finance Transformation
Currency [Currency] · last updated [timestamp]
Not ready · why?
State
Readiness checklist
  • Identity
    Owner: Trust & Verification
    Complete
  • !
    Payout profile
    Owner: you · resolvable
    Action needed
  • Market / program
    Owner: platform
    Supported
  • Provider requirements
    Owner: provider
    Met
Payout timeline
  1. Eligiblenow
  2. Initiated—
  3. Processing—
  4. Completed—
  5. Record retained—
Amount breakdown
Gross[Source-backed]
Payout fee[If applicable]
Tax / withholdingOmitted — no source value
NetFrom authoritative lines only
Destination & record
DestinationBank account •••• 4021
ConfigurationVerified by provider
Payout recordPO-••••-•••
Blocker: payout profile incomplete · owner: you · resolvable now.
What can affect progress

Every dependency,
and who owns it.

A professional reviewing payment dependencies at a laptop
No-timeout rule

No timeout implies acceptance, release, refund, cancellation, dispute resolution or payout completion — unless governing terms and the authoritative system explicitly support it and it was disclosed before commitment.

  • Active payment holdHold status, scope where allowed, reason category and next action. No invented adjudication.Payment Protection
  • Active disputeDispute-linked payment restriction, routed to Dispute Resolution.Dispute Resolution
  • Refund requested / pendingRefund state and affected amount when available; contradictory payout actions disabled.Refund & Cancellation
  • CancellationEffect on payment only when an authoritative rule or result exists.Refund & Cancellation
  • Change orderRe-evaluates version-bound release and payment eligibility.Contracts / milestone
  • Approval pendingShows the approval dependency — routing is not rebuilt here.Approval Workflows
  • Policy blockedShows the policy decision reference; never overrides it.Policy Engine
Fees, currency, tax & provider

Known before you commit
— never a surprise after.

Fees & Billing

A professional reviewing payment terms in a lounge
Before a paid action

You see the applicable amount, known fees, currency, mechanism/provider role where required, and relevant terms. Unknown values are never hidden behind a post-commitment surprise.

Disclosure component

Values from authoritative configuration
Amount

Authoritative engagement/payment amount and currency.

[Authoritative value]

Platform fee

Only the approved current value and responsible party; otherwise omitted.

[Approved value or omitted]

Provider fee

Only if applicable and source-backed, with the provider role if approved.

[If applicable]

Payout fee

Only if applicable to the professional, disclosed before commitment where required.

[If applicable]

FX / conversion

Rate, spread, source and timestamp only when conversion is actually performed.

[Only when converting]

Tax / withholding

Configured amounts/basis and responsible party only — no tax advice.

[Configured basis]

Net amount

Calculated only from authoritative lines; unknown fees or taxes are never treated as zero.

[From authoritative lines]

Terms

Link to the applicable payment/program terms and Fees & Billing.

Payment terms v[n]

Market availability

Supported, limited or unavailable for this payment capability.

[Market state]

Payment records & reconciliation

A durable record,
resolved to an exact version.

Explore payment records

Reference bundle

Sanitized
payment_record
PAY-••••-•••
payout_record
PO-••••-•••
provider_ref
where applicable · masked
contract / milestone
v4 / Milestone 2 v2
amount + currency
[resolved to payment version]
support_ref
SUP-•••• (non-sensitive)
Payment documents reviewed at a desk

Payment & payout states

Recommended normalization
Funding
Release
Payout
User-facing meaning
At least one governing dependency unresolved.
Source basis
Source-grounded concept
  • A release event does not imply a completed payout.
  • A payout is never shown as completed without authoritative completion evidence.
  • Amount and currency resolve to a specific engagement / milestone / payment version.
  • Material contract or milestone changes invalidate stale release readiness until recomputed.
  • Active hold, dispute, refund or cancellation states appear before any contradictory primary action.
  • Commands are idempotent — retries cannot duplicate money movement.
An open-plan office with teams working across markets
Availability by market & program

Supported, limited or unavailable — said plainly.

Universal currency or country coverage is never claimed. Availability is shown for your market and program before you rely on it.

  • Supported
    Capability available

    Funding and payout supported for this market and program under the applicable terms.

  • Limited
    Partially available

    Some methods, currencies or timing differ — the specific limits are shown.

  • Unavailable
    Not available here

    An approved alternative route is offered where one exists.

  • Source stale
    Status may be delayed

    The last confirmed state is kept and its freshness labelled.

A buyer funding an engagement on a tabletFund with clarity
A workspace ready for a reviewRelease with conditions
A professional at work in a bright officeTrack your payout
Questions

Payments
& Payouts,
answered.

A phone payment confirmation beside a wallet
Payment Support
A team planning an engagement around a table
Get started

Every step, accounted for.

Fund engagements, track payouts, or govern payments across your organization.

BuyersFind Professionals →ProfessionalsJoin as a Professional →EnterpriseEnterprise Access →

Payment methods, provider roles, fees, currencies, settlement/payout timing, protections and availability vary by supported market, engagement and program terms. ZoikoRum does not provide tax advice.