Cowrie Research

mansa-primary-sources-2026-05-07

5 min read

Mansa primary-source snapshot

Fetched: 2026-05-07 UTC

1) Official business homepage

Source: https://www.mansafinance.co/

Selected excerpts from the official site:

Unlock Instant Liquidity for Global Payments

Access instant liquidity to power your payments, eliminate delays and reduce prefunding requirements across markets.

Pay Globally, Seamlessly

Connect directly to local banking networks and digital wallets to pay suppliers and vendors globally.

Global Currency Solutions

optimizing FX flows and treasury positions through automated cross-border settlement and automated liquidity management.

Additional signals from the source:

  • The homepage frames Mansa around liquidity, treasury, and payout operations rather than consumer payments.
  • The repeated language around prefunding reduction and instant settlement points toward a capital-and-liquidity layer for operators.

2) What is Mansa?

Source: https://docs.mansafinance.co/introduction/what-is-mansa

Selected excerpts from the docs:

Mansa powers frictionless cross-border financial operations—delivering liquidity, speed, and regulatory confidence to global businesses and financial institutions.

Mansa replaces this with a single open API that orchestrates every stage of borrowing, disbursement, drawdown, utilization, settlement, and repayment

Additional signals from the source:

  • This is the clearest first-party statement that Mansa is not just a payout API; it is trying to own the full liquidity lifecycle.
  • Regulatory confidence is part of the product narrative, which matters for how the company should be classified.

3) Core concepts

Source: https://docs.mansafinance.co/liquidity/core-concepts

Selected excerpts from the docs:

All borrowers must be onboarded before they can access liquidity.

Who qualifies: Licensed money transmitters; Banks with cross-border services; Fintechs with payment licenses; Established remittance providers

A Loan represents a credit line extended to a borrower.

Disbursement occurs when Mansa moves approved loan funds into a Mansa-assigned wallet controlled for the borrower.

A Drawdown is when a borrower moves funds from their assigned custodial wallet … into their own third-party wallet.

Borrowers must demonstrate how withdrawn funds are used.

Each drawdown requires proof of utilization, tying liquidity directly to real economic activity.

Additional signals from the source:

  • The assigned-wallet versus borrower-wallet distinction is unusually important and makes the product look like monitored liquidity infrastructure, not a generic lender.
  • The proof-of-utilization requirement is also a major categorization clue because it turns liquidity into a compliance-heavy operating workflow.

4) Use cases

Source: https://docs.mansafinance.co/liquidity/use-cases

Selected excerpts from the docs:

With a single API, partners can borrow, disburse, draw down, and prove utilization of funds in real time—removing the need for capital buffers, manual processes, and settlement delays.

With Mansa, PSPs and MTOs borrow on-demand in stablecoins, disburse into monitored wallets, and draw down directly into payout corridors.

Impact: Remittance providers reduce corridor pre-funding by up to 70%, cut payout failures to near zero, and deliver faster, cheaper transfers to end users.

With Mansa, acquirers borrow per batch, disburse into their assigned wallets, and draw down to pay merchants.

Impact: Zero missed settlements and 30–40% reduction in float capital.

Additional signals from the source:

  • The use-case page broadens the picture from remittance into supplier payments, exchange liquidity, acquirer settlement, and payroll.
  • Mansa appears to sell capital efficiency and settlement timing as much as payment connectivity.

5) Settlement facility request endpoint

Source: https://docs.mansafinance.co/api-reference/v2/management/request-settlement-facility

Selected excerpts from the API reference:

Submit a new settlement facility request (V2 equivalent of loan request).

/api/v2/liquidity/management/settlement-facility

client_id

client_request_id

amount

chain_id

Additional signals from the source:

  • The public API surface for facility requests is a strong sign that liquidity provisioning is productized as software, not handled only by manual underwriting.
  • The presence of chain_id in the request reinforces the stablecoin- and network-aware nature of the facility.

6) Credit-limit endpoint

Source: https://docs.mansafinance.co/api-reference/v2/onboarding/get-credit-limit

Selected excerpts from the API reference:

Retrieve current credit limit and usage for the authenticated client.

available_credit

credit_limit

used_credit

currency: USDT

open_request

Additional signals from the source:

  • Mansa exposes ongoing liquidity capacity as an API primitive.
  • The credit-limit object makes the product look like a programmable credit line rather than a one-off settlement tool.

7) Whitelist endpoint

Source: https://docs.mansafinance.co/api-reference/v2/onboarding/add-wallet-to-whitelist

Selected excerpts from the API reference:

Add Wallet to Whitelist

/api/v2/liquidity/onboarding/whitelist

wallet_address

label

Wallet added to whitelist

Additional signals from the source:

  • Whitelisting destination wallets is exactly the kind of control-plane and compliance feature expected in a monitored liquidity system.
  • This also confirms that borrower-controlled operational wallets are intentionally bounded by policy.

8) Utilization-proof endpoint

Source: https://docs.mansafinance.co/api-reference/v2/utilization/create-utilization-proof

Selected excerpts from the API reference:

Submit a utilization proof record with supporting documents.

The request uses multipart/form-data.

The data field must be a JSON-encoded string containing the utilization payload.

Each proof document is attached as a separate file field named after the route or corridor it belongs to

/api/v2/liquidity/utilization/proofs

Additional signals from the source:

  • This is one of the strongest reasons to classify Mansa as a programmable liquidity control plane.
  • Route- and corridor-level proof attachments show the system is built around reconciliation, auditability, and policy enforcement, not just fast money movement.

Notes

  • Mansa appears best cataloged as programmable liquidity control plane / stablecoin-backed settlement-facility API / cross-border payments financing infrastructure.
  • No canonical standalone whitepaper or litepaper surfaced in this pass.
  • The strongest primary-source signals were the conceptual docs around disbursement/drawdown/utilization plus the API references for settlement facilities, credit limits, whitelists, and utilization proofs.

Graph View