NASPIP Protocol
NASPIP (Network-Agnostic Secure Payment Instruction Protocol) is an open-source standard for securely transmitting payment instructions across any payment network. Fluxis provides the premier API implementation of this protocol.
What is NASPIP?
NASPIP defines a secure, standardized data structure for payment instructions that works regardless of the payment network you want to use. It supports both traditional and cryptocurrency payment systems, offering:
- 🔒 Security: PASETO v4 public tokens with Ed25519 signatures for integrity and authenticity
- 🌐 Network Agnostic: Works with any blockchain or payment network
- 🤝 Interoperable: Open standard anyone can implement
- ⚡ Easy Implementation: Simple read/write operations via the Fluxis API or naspip-go
- 🎯 Flexible: Supports open/closed amounts and dynamic/static QR codes
Key Features
Secure by Design
NASPIP implements cryptographically signed payment instructions using PASETO v4 public tokens. Payers can verify token authenticity and payload integrity without trusting the transport channel. Fluxis handles key management, signing, and verification via the NASPIP API.
Universal Compatibility
Fluxis implements NASPIP for stablecoin payments on supported EVM networks (Polygon, Base, Avalanche, Arbitrum, Optimism, Ethereum, and others). See UAI for the current asset list.
User Experience Focus
Designed to improve cryptocurrency payment UX to match traditional payment methods, making blockchain payments accessible to everyone.
Why NASPIP?
Traditional payment methods have evolved to provide seamless user experiences, but cryptocurrency payments still face challenges due to:
- Multiple blockchains and tokens
- Complex technical information for users
- Lack of standardized payment instruction formats
- Security concerns in payment data transmission
NASPIP solves these challenges by providing a secure, standardized protocol that works across all payment networks.
NASPIP vs Fluxis API
NASPIP Protocol (Open Source)
The NASPIP protocol is open-source for anyone to implement. It defines:
- Data structures for payment instructions
- Cryptographic signing requirements
- Validation rules and specifications
- Interoperability standards
Fluxis API (Implementation)
Fluxis provides a production-ready API implementation of NASPIP that handles:
- 🔐 Automatic Key Management: No need to manage cryptographic keys
- 🔄 Auto-Rotating Keys: Enterprise-grade security
- 📱 QR Code Generation: Ready-to-use QR codes
- 🌐 Multi-Network Support: All major blockchains
- ⚡ High Performance: Scalable infrastructure
Fluxis NASPIP API
Fluxis exposes NASPIP token operations over the REST API (requires Bearer token + x-fluxis-api-key):
| Endpoint | Method | Purpose |
|---|---|---|
/v1/naspip/read | POST | Verify a NASPIP token and return parsed payload (PasetoCompleteResult) |
/v1/naspip/create | POST | Create a NASPIP token from payment instructions or a URL payload |
URL payload tokens: When a read token contains a url and no payment_options, Fluxis fetches payment instructions from that URL and returns them in payload.data (see Protocol Specification).
See the OpenAPI reference for request/response schemas.
Ready to get started? Sign up for Fluxis API and start integrating secure payments in minutes!