Request Network Guide for South African Crypto Invoicing and Payments
Request Network is a decentralised protocol and set of tools for creating, storing, and paying invoices on-chain, often in crypto or stablecoins.
Guide overview
Advanced freelancers, agencies, and Web3-native businesses who want transparent, tamper-resistant invoicing and payment records in crypto.
Execution blueprint
Overview
Request Network lets counterparties create and settle invoices on-chain, providing an immutable record of amounts, due dates, and payments. Interfaces built on top of Request offer dashboards, integrations, and automations. In MixtapeDB systems, Request might support high-trust, crypto-based B2B relationships and reporting, not everyday local invoicing for purely ZAR-based clients.
Setup process
Using Request responsibly requires clarity on who you invoice, in what currency, and under which legal framework.
Wallet and account
- Set up a secure crypto wallet (ideally hardware-backed) and ensure you understand gas fees and supported networks.
- Access Request-compatible apps via `https://request.network` or approved frontends; always confirm URLs to avoid phishing.
Creating invoices
- Define invoice details: payer address, amount, currency (e.g. stablecoin), due date, and description of services.
- Create the invoice through the app interface; it will be stored on-chain or in a decentralised format according to Request’s design.
- Share the invoice link or reference with your client, who can verify and pay via compatible wallets.
Settlement and records
- When the payer sends funds via the specified mechanism, the invoice’s status updates and the chain records the payment.
- Export invoice and payment data for your own accounting and tax records. Use Request’s APIs where available for automation.
South Africa execution notes
For South African operators, on-chain invoicing introduces additional regulatory and tax considerations. You remain responsible for issuing legally compliant invoices under South African law, even if the underlying record is on-chain. Exchange control rules may apply when receiving crypto from foreign clients, and SARS will treat amounts as income. Request Network is useful for transparency and automation but does not replace accounting, tax advice, or legal compliance.
Common pitfalls
Pitfalls include using volatile assets as invoice currency, poor documentation of exchange rates and tax treatment, and treating on-chain records as a replacement for formal invoices or contracts. Another risk is onboarding clients who are not comfortable with crypto payments, leading to friction and delayed cash flow.
Alternatives and substitutions
Alternatives include traditional invoicing tools (Xero, QuickBooks, local SA invoicing apps), other crypto payment gateways, or hybrid approaches where you invoice in fiat but also accept crypto via separate channels. For many South African businesses, traditional invoicing with optional crypto payment methods may be easier than fully on-chain invoicing.
Execution checklist
- Confirm which clients and services are appropriate for on-chain invoicing.
- Set up secure wallets and choose networks and currencies with acceptable volatility and fees.
- Create and test a small number of invoices end-to-end with trusted clients.
- Export and integrate invoice and payment data into traditional accounting systems.
- Review legal, tax, and exchange control implications with South African professionals.
Best-fit use cases
- Invoicing Web3-native clients in stablecoins with on-chain records.
- Automating crypto payment tracking for cross-border software and consulting work.
- Building educational case studies on transparent, decentralised invoicing.
Used in these systems
This tool appears inside real MixtapeDB income systems. Soon you’ll be able to download a curated systems pack gated behind ads.
Systems pack preview
See how this tool is wired into high-performing income systems.
Soon you'll be able to unlock a curated systems pack for this tool, gated behind ads for aligned partners. For now, explore the live systems below to see it in production.
FAQ
Practical answers for implementation and execution.
Is Request Network suitable for all my South African clients?
Probably not. Many South African clients will prefer standard ZAR invoices and bank transfers. Request fits better for Web3-native or international clients already comfortable with crypto operations and who see value in on-chain transparency.
How do I handle tax and accounting with on-chain invoices?
Treat income denominated in crypto as taxable at its ZAR value at the time of receipt. Keep records of invoice details, on-chain transaction hashes, and exchange rates. Work with an accountant familiar with crypto to integrate these into your books and SARS filings.
What happens if gas fees spike?
High gas fees increase the cost of creating and paying invoices. Consider using networks with lower fees (e.g. certain L2s) supported by Request, or batching operations when possible. Discuss fee implications with clients up front.
Can Request integrate with my existing tools?
Some Request-based apps offer APIs and integrations for accounting systems or internal dashboards. You can also build custom integrations using Request’s protocol documentation if you have development capacity.
Does on-chain invoicing guarantee that I get paid?
No. On-chain records improve transparency and reduce disputes, but they do not force payment. You still need contracts, trust, and collection processes, just as with traditional invoicing.
Disclaimer and sources
Use this guide as educational input, not as financial, tax, or legal advice.
Important disclaimer
This guide is for informational purposes and does not represent Request Network. It is not legal, tax, or financial advice. South African users must ensure that any use of Request complies with local law and professional guidance.
Last reviewed: 2026-03-05