​
Build your payment flow

OurPay brings products, hosted checkout, orders, subscriptions and customer access into one API and dashboard. Choose the payment methods that fit your customers, and keep the resulting business records together. Availability depends on the payment method, network and account configuration.

Domestic INR

UPI and bank transfers go to the seller’s configured receiving account. Automatic confirmation requires an approved bank integration.

USDC

Collect supported USDC payments into the configured OurPay wallet and follow network confirmation before completing the order.

PayPal

Use the eligible PayPal checkout and subscription flows, with provider fees and payment records visible separately.

​
Start with a product

1

Create an organization

Sign up for OurPay, create your organization and review its payment settings.
2

Create your product

Set its name, price and billing model. Attach benefits such as a download or license key where needed. See products.
3

Share a checkout

Create a checkout link, or create a session from your backend using the API.
4

Connect your application

Process signed webhooks and use verified order or subscription state to manage access.

​
Follow the payment through

A buyer opening a payment app, submitting a bank receipt or broadcasting a wallet transaction is not the same as a confirmed payment. The payment method determines what evidence is required before an order can complete. For UPI, an ordinary QR authorizes a single transfer. Recurring automatic debits require a supported mandate integration. For USDC, one-time network support and recurring-payment activation are separate capabilities. Read the collection guide before enabling a method.

​
Build with the API

TypeScript SDK

Use typed requests and responses from your server-side application.

Python SDK

Use the synchronous or asynchronous client in a Python backend.

Next.js guide

Create checkout sessions and handle signed webhooks.

REST API

Integrate with the documented endpoints from other languages.
Keep organization access tokens on your server. Use stable customer identifiers and idempotent event processing so retries do not duplicate business actions.

​
Beyond checkout

  • Subscriptions: lifecycle, changes and payment-method capabilities.
  • Usage meters: count activity and connect it to pricing.
  • Cost insights: compare customer revenue with provider and infrastructure costs.
  • Customer portal: give customers access to purchases and supported account actions.
  • Benefits: connect paid access to files, licenses and supported integrations.
  • Finance: review recorded balances, fees and seller liabilities.

​
Know the operating model

Collection, merchant payouts and tax operations are separate parts of the system. A collected payment or ledger balance does not mean a payout has been executed. Your organization remains the invoice issuer; enabling a feature does not establish a bank partnership or transfer legal responsibility. Review fees, payout behavior and the payment model. Your account’s configured plan and enabled providers determine the applicable behavior.

​
Explore OurPay

Read Introducing OurPay, browse the journal, or explore the API reference.
Documentation illustrations use example values to explain workflows. They are not customer records, testimonials or proof of production payment activity.