flutterwave_ke
SELECTED
flutterwave_ke healthy
paystack_ng degraded
pawapay_ke healthy
stitch_za healthy
The brand identity for Orchura — a payment orchestration layer engineered for heterogeneous rails, for sponsor banks, regulators, and the developers who actually read the docs.
What Orchura is, what it stands against architecturally, and the one sentence everything else hangs from.
Why ‘Orchura’ — etymology, sound, and the words it must never be confused with.
The wordmark, the symbol, and how they lock together on dark and light surfaces.
Obsidian canvas, emerald accent, bone type. The full palette and where each colour earns its place.
Inter for system, Fraunces Italic for emphasis, JetBrains Mono for evidence.
How Orchura writes — with principles, examples, and a list of words it does not use.
The grid, the rules, the durations, and the quiet moves that make the system feel composed.
Ten beliefs that govern every design decision. When this document doesn't cover the case, these do.
How the visual system handles the period before launch — what's shown, what's labelled, what waits.
The brand applied. Hero, dashboard chrome, business card, social post, email signature.
What moved between V1.0 and V1.1, and why.
A payment orchestration layer. A single API above sponsor banks, card processors, mobile money aggregators, Pay-by-Bank providers, and stablecoin rails — engineered as one system from the first ledger entry. Every transaction routed to the path most likely to succeed at the lowest defensible cost, settled into a double-entry ledger that survives audit, reconciled back to the rail of record without human intervention.
Not a wallet. Not a neobank. Not a card scheme. Not a crypto exchange. Not a low-code workflow builder. Not a marketplace of integrations someone else built. Not a thin wrapper that breaks the moment a rail changes its API.
Engineering-led B2B merchants, marketplaces, and treasuries that have outgrown the single-PSP setup and refuse to staff a payments engineering team to escape it. Companies whose founders read the API docs themselves.
Anyone who wants a sales rep. Anyone whose evaluation criterion is whether we appear in a Gartner quadrant. Anyone whose first question is the discount.
Two architectural patterns dominate the existing market. Orchura's position is defined by being neither.
Gr4vy, Spreedly, Primer. Architecturally mature, US/EU-built, expensive. Each was extended outward from international card processing and treats mobile money, Pay-by-Bank, and instant rails as connectors retrofitted onto a card-shaped core. The pattern is correct; the order in which rails were added shaped the codebase. Excellent for retailers whose volume is mostly cards.
Flutterwave, Paystack, Yoco, Razorpay, Mercado Pago. Each is a payment processor pretending to be an orchestrator when the pitch deck calls for it. Excellent at being one rail. The merchant still hits a ceiling at the second country, and the ceiling is the aggregator's own balance sheet.
Engineered. Not assembled. One orchestration system designed for heterogeneous rails from the first commit — cards, mobile money, Pay-by-Bank, instant settlement, and stablecoin as peers in the codebase, not connectors retrofitted on top.
The launch corridor is South Africa, with extension into SADC and selected sub-Saharan corridors. Geography is where Orchura starts; it is not what Orchura is. The brand does not lead with "African" or "pan-African" — the architectural claim generalises beyond any single continent, and leading with geography invites every conversation to be about the team's identity rather than about the system. The corridor catalogue belongs in the docs and the rail matrix, not in the headline. See Brand Story V1.0 §02 for the full reasoning.
Orchura is a coined word with two roots. The 'orch-' opening carries the sense of orchestration — composing many parts into a single performance — without using the word itself. The '-ura' ending is borrowed loosely from Latin and Romance languages, where it forms abstract nouns of process and action: 'natura', 'cultura', 'infrastructura'. The combined effect is a name that sounds like it has always existed without belonging to any specific language family.
Three syllables. Stress on the second. The 'ch' is hard, as in 'orchestra' — never soft as in 'church'. This matters: the soft 'ch' makes the brand sound like a candle company, which it is not.
‘Orchestrate’, ‘Conductor’, ‘Maestro’, ‘Compose’ are all taken — by music apps, project tools, container schedulers, and at least three other fintechs. ‘Rail’, ‘Route’, ‘Flow’ are the words every competitor reaches for first. Orchura sits adjacent to the obvious vocabulary without using any of it. That distance is the point.
The wordmark is set lowercase in Inter Black with negative letter-spacing tightening it into a single visual unit. Lowercase is deliberate: lowercase reads as software, uppercase reads as a sponsor bank. We are software.
A chevron-and-circle composition forming an abstract ‘O’ around an upward-pointing inflection. The chevron carries the orchestration metaphor (a conductor's mark) without making it literal. The circle frames it as a complete system, not a stand-alone glyph. Two grades — outline-heavy for favicon, balanced for app icon and large applications.
Obsidian is the canvas. Not pure black — a near-black with a faint green undertone, so when emerald sits next to it the two read as part of the same system instead of accent on background. Emerald is the only saturated colour in the brand; it carries every ‘this is Orchura’ signal. Bone is the type colour on dark — warm off-white, never pure white, because pure white on near-black creates eyestrain at body sizes.
When a single canvas isn't enough — cards on cards, panels within panels — these graphite tints stack. Each is built from obsidian with progressively more lift, so the eye reads them as the same surface at different elevations.
Three tiers. Bone for primary text and headlines; ash for secondary copy, captions, and metadata; smoke for the deepest tertiary — page numbers, footer marks, the things you should be able to find but should not be reading.
If something is rendered in emerald, it must be one of three things: a wordmark or symbol, an interactive element (a link, a button, a focusable control), or a positive state confirmation (success, available, healthy). When in doubt, render in bone or ash and ask whether emerald earns its place.
Two more colours exist. Both are reserved for state communication and forbidden in any decorative role.
Amber: warning state, trade-off flags, pending confirmation. Signal: critical only — failed payment, security alert, severed connection. Neither colour appears in marketing material, in the wordmark, or in the chrome of the product.
When a deliverable must be light (an invoice, a printed contract, a regulatory submission), the canvas inverts: paper as background, ink as type, emerald unchanged. Bone-on-paper is invisible — never use it. Light surfaces are the exception, not the system; reach for them only when the deliverable demands it.
Body, UI, headlines, buttons, navigation. Every default. Inter handles a wide range of Latin-extended diacritics without falling back to inferior fonts. Inter Display for headlines (32px+); Inter for everything below.
Italic emphasis only. Used inside otherwise-sans headlines to draw the eye to one word. Never used at body sizes; never used upright. The only serif in the system. (Production hint: upgrade to Tiempos Headline Italic if budget allows; Fraunces is the strongest free alternative.)
Section labels, code, ledger numbers, transaction IDs, anything where a number must be unambiguous. The brand's fingerprint when nothing else identifies it. Tabular figures always on.
Almost every Orchura headline follows one pattern: an upright sans statement with one italic serif word inserted as emphasis. The italic word is always the verb or the adjective that carries the meaning.
One italic word per headline — never two, never zero. The italic word is the meaning the brand stands behind; everything else is structural.
Orchura's voice is the voice of someone explaining how their machine works to a peer. Not a salesperson. Not an evangelist. Not a copywriter performing enthusiasm. The reader is intelligent and busy. The brand is competent and wants them to leave with what they came for.
‘Routes a card payment to Flutterwave when the issuer BIN matches a Kenyan bank.’ Not ‘intelligently routes payments for optimal performance’.
Tell the reader what we do, not how it will make them feel. They will work out the benefit themselves; that's why they're reading.
‘Sub-200ms p99 routing decision.’ Not ‘blazing-fast’. Where a number isn't honest, omit the claim.
No re-statement. No ‘in summary’. No closing flourish. The white space after the last sentence is part of the message.
Some vocabulary is cheap. Some is dangerous (it makes legal claims we can't substantiate). Some just makes us sound like every other fintech. All of it is forbidden in Orchura's external writing without an explicit exception.
These aren't mandatory, but they pattern the voice. ‘Compose’ over ‘build’. ‘Settle’ over ‘process’. ‘Reconcile’ over ‘match’. ‘Route’ over ‘send’. ‘Resolve’ over ‘handle’. ‘Defensible’ over ‘good’. ‘Sub-200ms’ over ‘fast’.
12 columns, 24px gutter, 96px outer margin on desktop. Mobile collapses to 4 columns at 16px gutter. The grid exists to make alignment effortless, not to be visible — when a layout decision feels like fighting the grid, the grid is right.
Spacing is built on an 8px base unit. Every margin, gap, and padding value is a multiple of 8. Six values cover almost every case: 8, 16, 24, 48, 72, 144. Anything outside this set requires justification.
Every section opens with a small uppercase mono label in emerald or ash, with letter-spacing roughly +22%. The brand's most consistent visual fingerprint.
Headlines sit upright in the sans, with one word swapped to Fraunces italic. The italic word does the meaning-work; the upright words frame it.
Where a typical brand draws a horizontal line, Orchura draws nothing — and lets the white space carry the break. Where a divider is unavoidable, it's a single hairline at #2A322F, 1px, never thicker.
Dashboards are dense. Marketing is generous. The contradiction is intentional: the product earns trust by showing the operator everything at once; the brand earns trust by giving the prospect room to think. The same colour palette and typography binds both.
4px on inputs and small buttons. 6px on cards. 8px on panels and large containers. 12px on modals. 0px on full-bleed sections and tables. No values in between, ever.
Orchura's product handles money. Animation that exists to entertain — bouncing icons, rotating logos, parallax scroll — undermines the trust the rest of the brand spends so much effort earning. Every animation must answer: what state changed, and how do I show the user it changed?
Anything longer than 480ms is a loading state, and loading states need a different treatment — a skeleton, a progress indicator, or honest text. Never a spinner pretending to be a feature.
Show how the system works and the trust takes care of itself. Don't perform competence; demonstrate it. A cleanly-rendered routing diagram is worth more than three paragraphs of ‘intelligent orchestration’.
Every screen, every document, every piece of marketing is designed for the person who has to use it on Tuesday morning. If it looks great in a portfolio but slows the operator down, it's wrong.
Most of the brand is bone, ash, and obsidian. Emerald only appears where it does work. The discipline of withholding colour is what makes the colour mean something when it arrives.
Wherever a claim can be expressed as a number, express it as a number. Where it can't, the claim probably shouldn't be made.
When a headline runs upright and one word leans, that word is the verb the brand stands behind. Choose it deliberately. ‘Composed.’ ‘Settled.’ ‘Resolved.’ Never ‘revolutionary.’
Every component, every page, every documentation surface treats cards, mobile money, Pay-by-Bank, instant settlement, and stablecoin as peers. The brand never visually privileges one rail family — the rail matrix lists them in alphabetical or coverage order, the marketing examples cycle across them, the dashboard's empty states show all of them. Where the launch corridor is South Africa, the brand says so explicitly; it does not generalise to "global" or shrink to "African". The rails are the subject. The geography is the deployment.
When the brand has to choose between looking exciting and looking trustworthy, it chooses trustworthy. A sponsor bank or a SARB examiner should be able to read any Orchura surface and find nothing alarming. The developers will find the depth on their own.
Orchura runs dark. Not because dark mode is fashionable; because the product is a financial control surface, and dark canvases reduce eye strain over the long sessions operators actually spend with the dashboard. Light surfaces are the exception.
Every component, page, and module is designed to slot into a larger system someone else is building. Orchura is the orchestration layer; its brand should feel like one too. Self-contained set pieces are weaker than reusable parts.
Almost every design weakness in this brand will come from adding too much. The instinct is to add. The discipline is to remove. If a screen still works after a deletion, the deletion was correct.
This section is the visual companion to Brand Story V1.0 §04. Where the story document defines what the brand may say at each stage, this section defines what the brand may show.
For surfaces that need to record their state — investor decks, technical documentation, product preview pages — the stage badge sits in the same visual register as the version metadata. Three forms.
M0–M16. Used on investor decks, sponsor-bank briefings, technical documentation, and the developer portal cover. Sits in the cover-bottom strip alongside the version number.
M16+. Replaces [BUILD] on the day Phase 1 sign-off is recorded. The switch-over is binary; documents are not republished as "soft launch" or "early access" or any intermediate state.
Per-endpoint or per-feature, used inside developer portal. An endpoint or SDK can be PREVIEW after the rest of the platform is LAUNCH. The badge attaches to the surface, not the company.
The day Phase 1 sign-off is recorded, every external document, deck, and surface bearing the [BUILD] badge is updated to [LAUNCH]. The boilerplate switches (per Brand Story §09). The marketing hero is unchanged — its language was already launch-stage. The investor deck cover gets a one-character edit. The developer portal endpoints with sufficient production stability move from PREVIEW to STABLE. The brand does not announce the switch-over; it just stops being in build, and the world reads the change in the badges.
Dark canvas, generous vertical white space, single italic word in the headline, mono kicker label, one emerald CTA. The product UI screenshot does the heavy lifting; no abstract 3D imagery, no stock photography.
Sidebar in graphite, content in obsidian, accent in emerald, type in bone and ash. Numbers always in mono. Status indicators are dots in emerald (healthy), amber (degraded), or signal (down). No avatars. No gradient buttons. The chrome should disappear so the data shows through.
85mm × 55mm. Front: symbol in emerald, centred, large. Back: name in bone, role in ash, contact in mono. No QR code. No tagline. The card is a name, not a brochure.
Single statement. One number. Mono-tagged source. No image. No emoji. No hashtag. Posts that need decoration to land aren't worth posting.
Plain text. No images. No social icons. Three lines.
V1.0 framed Orchura as a pan-African brand built in South Africa for the continent. V1.1 reframes Orchura around its architectural claim — a payment orchestration layer engineered for heterogeneous rails — with geography treated as the launch corridor, not the brand identity. The visual system is unchanged. The wordmark, symbol, palette, type scale, layout grid, motion rules, and voice principles are all preserved. The content moved; the identity did not.
Three forces drove the change. One, the legal entity is Orchura, Inc. (Delaware) with an SA operating subsidiary; "built in Africa, for Africa" was no longer accurate as written. Two, the architectural claim — heterogeneous rails as a first-class concern, against orchestrators that extended outward from cards — is structurally stronger and harder to copy than the geographic claim was. Three, the geographic frame painted the brand into a corner that V1.0 had already started leaking out of through Phase 2 (which is global by construction, not African).
V1.1 of this identity is binding alongside Brand Story & Positioning V1.0, which is the narrative companion. Where the two disagree on a point of brand direction, the more recent document wins; where this identity is silent and the story document is not, the story document governs. Both supersede all prior naming, marks, and visual references for the project.