Anypay primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is Anypay’s GitHub org, especially the core server README, the TypeScript SDK README, and adjacent wallet/checkout tooling READMEs.
• The materials consistently frame Anypay as non-custodial merchant-payment and payment-request infrastructure rather than as a single hosted wallet or simple checkout widget.

Primary-source snapshots

1) Core server README

• URL: https://raw.githubusercontent.com/anypay/anypay/main/README.md
• Key excerpt:
  • The README says Anypay exists to help developers create apps that transfer “any kind of value on any open system,” with a specific focus on retail digital-cash payments.
  • It says Anypay addresses incorrect amounts, invalid addresses, slow payments, failed confirmations, double-spend fraud, and accidental double payments.
  • It explicitly documents support for multiple payment protocols: JSON Payment Protocol, BIP70, BIP270, and pay://.
  • It also lists a broad native asset surface across Bitcoin-family chains, Monero, XRP, Ethereum, Solana, Polygon, Avalanche, and several stablecoins.

2) TypeScript SDK README

• URL: https://raw.githubusercontent.com/anypay/anypay-sdk/master/README.md
• Key excerpt:
  • The SDK says applications can request payments to multiple addresses in multiple cryptocurrencies while ensuring funds are never held by any third party.
  • It documents direct integration primitives such as webhook_url, redirect_url, shared-secret verification, and merchant metadata.
  • Example requests cover BTC, DOGE, BSV, and stablecoin flows on Ethereum, Solana, and XRP-linked assets, which makes the SDK look like real merchant/payment infrastructure rather than only an internal helper library.

3) Simple wallet / protocol client README

• URL: https://raw.githubusercontent.com/anypay/simple-wallet/master/README.md
• Key excerpt:
  • The simple-wallet README says the wallet implements the JSON Payment Protocol V2 spec and is compatible with AnypayX.com and Bitpay.com.
  • It shows a client flow that fetches payment options from an Anypay invoice URL, selects a payment option, and sends the payment with wallet tooling.
  • This is strong evidence that Anypay is standardizing an actual interoperable invoice/payment-request workflow rather than merely generating QR codes.

4) Web3 checkout widget README

• URL: https://raw.githubusercontent.com/anypay/web3-checkout/main/README.md
• Key excerpt:
  • The checkout-widget README documents a popup widget keyed by invoice ID and configured with success/failure callbacks.
  • That surface reinforces that Anypay packages frontend merchant-checkout UX on top of the protocol and server layers.

Working conclusion

Anypay is best cataloged as non-custodial payment-request and checkout infrastructure: a stack that tries to normalize invoice creation, protocol negotiation, wallet-compatible request handling, and merchant callbacks across multiple crypto payment formats and chains. The decisive evidence in this pass was the repeated combination of non-custodial language with concrete server, SDK, wallet, and widget tooling.