KeyBS Pay (keybs.io)

KEYBS PAY (KEYBS.IO)Manage supplier listing

Realized cross-border payout execution data generated as a byproduct of moving money: per-corridor locked FX rates quoted at approval (e.g. NGN to KES), rail-level settlement latency from submission to confirmed webhook (real-time local rail vs same-day batch vs T+0 to T+2 wire), per-rail transaction limits, quote-based fee structures by rail/method/volume, routing decisions (which local rail was eligible and chosen at that moment) and beneficiary bank-validation/fraud/AML-screen outcomes across 190+ countries, 80+ currencies and 48 payment rails

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks KeyBS Pay (keybs.io) and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Transaction & Settlement Services
Instruments: fx
Categories: AlternativePriceSupply Chain

Dataset card

Type: not stated
Format: Event-stream / tabular — signed HMAC webhooks emitted on every payout state change, an idempotent payout API, and per-corridor reconciliation records; consumer surface is per-corridor landing pages
Volume: Order 10^4-10^5 payout events over its operating life at modest scale, but structurally rich — every event carries corridor, rail, locked rate, fee, timestamped state transitions and screen results, and the site exposes a large corridor matrix (country-pair, rail and industry pages, including an MTN MoMo rail page) implying dozens of monitored corridors and 48 rails
Users: N/A as a consumer metric — B2B only: businesses onboarded after KYB review, count undisclosed. Corporate contact records show a micro-team Accra-based operation, implying a client base in the tens to low hundreds rather than thousands
History: 2 years
Update frequency: not stated
Growth: Active build-out — a newly launched enterprise payout product with a programmatically generated corridor/rail/industry page set and operational API surfaces (webhooks, idempotency, reconciliation), no sign of decline
Launched: est. 2024-2026 — no copyright year, changelog, funding round or press mention appears on the fetched pages, but the vendor's contact-record entry is a recent addition to business databases and the corridor-page system is a modern generated-content architecture
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site