arf

• Name: arf
• URL: https://arf.one/
• Category: regulated cross-border-payments liquidity company / receivables-backed settlement operator / stablecoin-assisted working-capital control plane
• Tags: ethereum-ecosystem
• Summary: arf belongs in companies/, not just projects/, because the durable dependency is a named regulated operator packaging client admission, receivables-backed credit approval, repayment timing, bank-and-chain settlement endpoints, request-signing policy, and transparency publication inside one company-run shell. The useful question is not only what Liquidity API does arf expose? but which company decides who gets funded, on what repayment terms, through which bank and chain rails, and with what reporting and compliance posture?
• What it does:
  • Extends short-term, receivables-backed liquidity to licensed cross-border payment companies so they can reduce destination-market prefunding
  • Targets regulated financial institutions rather than retail users, with official materials explicitly limiting service to licensed entities
  • Packages stablecoin-linked and onchain-visible settlement workflow as operational plumbing around the credit product rather than as the product’s only point
  • Exposes a company-run Liquidity API for client onboarding, bank-information and chain-information registration, credit simulation, and credit-request submission
  • Maintains a public transparency surface and dashboard for aggregate liquidity and onchain activity metrics, which turns publication policy into part of the practical trust shell
• Key claims:
  • The homepage calls arf a regulated liquidity and settlement platform for cross-border payment companies and says it provides services only to licensed financial institutions
  • Product materials describe arf Liquidity as short-term receivables-backed working capital with 1-5 day repayment terms and no collateral requirement, which makes operator underwriting and repayment workflow more important than any abstract protocol story
  • Official copy repeatedly frames prefunding elimination as the core value proposition, which means the real dependency is arf’s company-managed credit and settlement shell rather than a neutral payments primitive
  • The transparency page says loans, repayments, and receivables can be traced onchain and links to a live dashboard, making onchain publication and company-authored interpretation part of the trust surface
  • The Liquidity API docs expose concrete sandbox/live environments, RSA-4096 request signing for sensitive endpoints, and credit-check / credit-create workflows tied to named client profiles, which is strong evidence that the real control surface is admission and workflow management by a regulated operator
• Whitepaper: No classic standalone company whitepaper is the point here. The clearest primary materials are arf’s official site, liquidity and transparency pages, and the Liquidity API docs; the primary-source bundle remains ../whitepapers/arf-primary-sources-2026-04-26.md.
• Sources:
  • https://arf.one/
  • https://arf.one/arf-liquidity/
  • https://arf.one/transparency/
  • https://docs.arf.one/
  • https://docs.arf.one/introduction-1261159m0
  • https://docs.arf.one/environments-1261176m0
  • https://docs.arf.one/authentication-1261164m0
  • https://docs.arf.one/create-client-18921877e0
  • https://docs.arf.one/create-bank-information-20886802e0
  • https://docs.arf.one/create-chain-information-20886804e0
  • https://docs.arf.one/check-credit-18921900e0
  • https://docs.arf.one/create-credit-18921921e0

Internal linkages

• Project-layer alias note: arf.
• Useful adjacent company reads: openpayd, orbital, bvnk, and modern-treasury.
• Lower-layer contrast where the question becomes payment-initiation or interoperability standards rather than one regulated credit-and-settlement operator: open-payments.

Protocol / company boundary

• arf does not read like a neutral protocol or standalone network whose deployed mechanics explain the main dependency.
• The analytically important surface is the company-run operating shell that packages client admission, receivables-backed credit approval, repayment timing, bank and chain settlement endpoints, request-signing policy, transparency publication, and the broader legal/compliance perimeter inside one inherited vendor workflow.
• That is why arf belongs in companies/: the real leverage sits with the named operator that controls funding access and settlement choreography, not with an abstract cross-border liquidity API label.

Control surface

• Practical authority sits in customer admission, bank-information and chain-information acceptance, credit simulation and approval, repayment-term setting, settlement-rail configuration, sensitive-request signing policy, transparency publication, and which lifecycle states counterparties treat as authoritative.

• The sticky dependency is workflow memory: once a payments company builds around arf-managed client profiles, credit decisions, settlement rails, request-signing expectations, and dashboard / transparency outputs, the lock-in is to the company-run operating shell rather than to a generic stablecoin or cross-border settlement primitive.

• Read arf as a regulated operator boundary first. The API is distribution; the real control surface is the company shell behind funding, settlement, and compliance workflow.

• Last reviewed: 2026-08-12 UTC