Cowrie Research

request-finance-primary-sources-2026-04-29

4 min read

Request Finance primary-source snapshot

Last reviewed: 2026-04-29 UTC

Project status snapshot

What the official materials say

1) Request Finance docs: AP/AR and payroll product framing

  • URL: https://docs.request.finance/welcome.md
  • Key takeaways:
    • The docs say the API lets users issue invoices, accept payments in crypto and fiat, track invoice status without polling chains or bank accounts, and create salary payments in crypto and fiat.
    • This makes Request Finance look like finance-operations infrastructure for businesses rather than merely a payment button or checkout widget.
    • The docs are clearer than the homepage about the exact operating surface.

2) Invoices docs: off-chain object first, onchain request second

  • URL: https://docs.request.finance/invoices
  • Key takeaways:
    • Request Finance says users first create an invoice off-chain, then convert it into an onchain request.
    • The docs explicitly state that Request Network payment requests are stored onchain and that Request Finance invoices are a predefined-schema implementation of those requests.
    • This is the single most important architectural clue for cataloging the project: Request Finance is an application/API layer on top of Request Network, not an entirely separate protocol.

3) Payroll docs: salary and vesting flows as another request type

  • URL: https://docs.request.finance/salaries
  • Key takeaways:
    • The payroll docs say Request Finance can pay net salaries, bonuses, or token vestings.
    • Technically, a payroll payment is handled as another invoice type and still needs conversion into an onchain request.
    • The format field rnf_salary is what makes the payment appear as payroll in the Request Finance application.
    • This shows the platform is really a finance-operations schema and workflow layer over the same request substrate.

4) Request Network docs: underlying protocol scope

  • URL: https://docs.request.network/readme.md
  • Key takeaways:
    • Request Network says developers can build invoicing, crypto payments, and invoice/payment reconciliation.
    • The docs describe request creation, payment facilitation, webhook notifications, fee collection, and partial-payment support.
    • The protocol framing is broader than a single Request Finance product flow, which helps explain why Request Finance sits best as the business-facing layer atop Request Network.

5) Request Network site: crypto-payments and reconciliation narrative

  • URL: https://request.network/
  • Key takeaways:
    • The site frames Request Network around getting paid and paying in crypto, with messaging about coverage, low-cost money movement, and payment accounting.
    • While the marketing site is more generic than the docs, it reinforces the reconciliation-and-request positioning.
    • The docs still provide the sharper technical source of truth.

6) GitHub orgs: protocol depth versus application-layer thinness

  • URLs:
  • Key takeaways:
    • The verified RequestNetwork GitHub org describes itself as “The protocol for requests, payments, and 100% automated reconciliation.”
    • Pinned repos include docs, an invoice demo app, request-scan, a token list, and the requestNetwork JavaScript library.
    • The RequestFinance GitHub org is much thinner and mostly exposes docs plus supporting tooling like the rf CLI and small utility repos.
    • This asymmetry reinforces the category placement: Request Finance is the operational API/application layer; Request Network is the deeper protocol layer.

Whitepaper / technical-doc status

  • No canonical standalone Request Finance whitepaper or litepaper surfaced in this pass.
  • The primary-source corpus is split across two linked first-party surfaces:
    • Request Finance docs for the product and operational workflow layer
    • Request Network docs and GitHub org for the underlying protocol and developer stack
  • For most users of the library, both need to be read together to understand the real architecture.

Research notes

  • Best current category for the library: crypto accounts-payable and accounts-receivable infrastructure / invoicing-and-payroll control plane / Request-Network-based payment operations.
  • The key insight is that Request Finance is not just “crypto invoicing software”; it is a business-facing workflow layer that serializes invoices and payroll items into Request Network payment requests.
  • The second key insight is the separation of concerns between the two brands: Request Network holds the protocol / SDK / node narrative, while Request Finance holds the finance-ops application and API narrative.
  • This makes the pair a strong example of a crypto-adjacent control plane layered on top of a decentralized payment-request protocol.

Graph View