Transparency
Methodology
How the platform works, and where it stops. We aim to back every number on this site with a defined method, and to say so when something is not built.
How we choose the rail
FinVeil's routing engine scores every eligible provider and rail for a routed transaction, selects the highest total score, and records the decision and its fallback order. Each option is scored on four dimensions:
- Cost — from provider rate cards with a recorded source. A rate FinVeil cannot source scores 0, so an unknown rate never looks cheapest.
- Speed — a fixed score per rail type (PayShap highest, EFT lowest). It is not a measured settlement time.
- Reliability — the provider's 24-hour success rate; a provider with no track record scores 70.
- Bank match — whether the provider supports the recipient's account type.
The weights come from the routing mode (instant, same-day, cheapest, or default collection). Failover along the recorded fallback order runs in test mode only; automatic live failover is on the roadmap. Paystack is verified end to end in test mode; Ozow and Stitch (PayShap) are not yet connected.
How Transaction Proof works
Each settled transaction gets a SHA-256 proof receipt. Every hour, receipts not yet batched are combined into a Merkle root, which FinVeil stores in its own database. The Merkle leaves are hashes of the receipt IDs, so a batch shows which receipts existed at that time; it does not by itself prove the amounts.
A receipt can be checked on FinVeil's public verification page (/verify/receipt/{receiptId}), which calls FinVeil's API. Anchoring to a public ledger (such as Stellar) is not live, so verification depends on FinVeil's servers.
How we match settlements
Settlement matching is not built. Today, reconciliation is a tally of FinVeil's own transaction records by status (completed versus not completed). Nothing is matched against provider settlement reports or bank statements yet.
Platform uptime
Uptime is not yet measured or published. Plan-level uptime targets are on the pricing page. The Status page is not an uptime record.
Legacy product
Wellness Suite methodology (legacy product)
The sections below describe the stress-scoring model that powers FinVeil's Wellness Suite. New deployments should start from the payment-orchestration methodology above.
Stress scoring
FinVeil uses a 6-factor rule-based model derived from payroll data to generate employee financial stress scores. Each factor adds a fixed number of points. The weights are FinVeil's own rules, not a statistically fitted model:
- Presence of garnishee orders
- Loan deductions as a percentage of gross pay
- Net-to-gross pay ratio
- Number of concurrent loan deductions
- Salary band positioning
- Declining net pay trend over 3+ months
Scores range from 0 to 100 and map to four risk levels: Low, Moderate, High, and Critical. Full scoring details are available on the Stress Score product page.
Early-stage transparency
FinVeil is a pre-revenue platform and has not processed live customer volume. Results will be published here only once there is real data. We do not cite third-party statistics without attribution, and we do not fabricate case-study numbers.