# InFlow payments

> Integrate applications that accept or make payments through InFlow using MPP and x402.

Begin with the guided integration workflow. It establishes Buyer and Seller
responsibilities, examines existing capabilities, and creates an approved plan
before implementation. Keep authentication and payment decisions explicit.
Do not initiate payments merely to explore an integration.

## Integration

- [Guided InFlow integration](https://app.inflowpay.ai/integration.md): Add or expand payment support one approved step at a time.
- [Integration plan template](https://app.inflowpay.ai/integration-queue-template.md): Maintain INFLOW-INTEGRATION-PLAN.md from repository confirmation onward.

## SDK and protocol references

- [InFlow Go SDK](https://github.com/inflowpayai/inflow-go): Go Buyer and Seller packages and runnable examples for MPP and x402.
- [InFlow Node SDK](https://github.com/inflowpayai/inflow-node): Node.js and TypeScript Buyer and Seller packages and runnable examples for MPP and x402.
- [InFlow Python SDK](https://github.com/inflowpayai/inflow-python): Python Buyer and Seller modules and runnable examples for MPP and x402.
- [InFlow Rust SDK](https://github.com/inflowpayai/inflow-rust): Rust Buyer and Seller crates and runnable examples for MPP and x402.
- [MPP protocol](https://mpp.dev/): MPP protocol documentation.
- [x402 protocol](https://www.x402.org/): x402 protocol documentation.

## Accounts and environments

- [Sandbox](https://sandbox.inflowpay.ai): Account and credential setup for testing.
- [Production](https://app.inflowpay.ai): Account and credential setup for live integration.

Choose the account role for the selected API path. Configure the SDK environment
explicitly and never include credentials in chat or an integration plan.

## Separate integrations

- [ODP integration](https://www.offeringprotocol.org/integration.md): Catalog discovery.
- [AEP integration](https://www.aep.foundation/integration.md): Enrollment and authentication.