Everything is a productSubscriptions and one-time purchases are both products in OurPay — same API, same data model, just different pricing and billing logic. They live together in the Products dashboard, filterable by pricing model.

​
Billing cycle

A product is either a one-time purchase or recurring. One-time products charge the customer once and grant access forever. Recurring products bill on an interval — daily, weekly, monthly, or yearly — and you can extend any of those with an interval count to express things like “every 2 weeks” or “every 3 months”. The billing cycle and recurring interval are locked in at creation. If you need to change them later, create a new product instead.

​
Pricing

OurPay supports several pricing models, and you pick one per product:
  • Fixed price. Set an amount and that’s what customers pay.
  • Pay what you want. Customers choose the amount. You can set a minimum and a default that’s pre-filled at checkout.
  • Free. No charge. Useful for lead magnets, free tiers, or gating benefits behind a sign-up.
  • Metered pricing. Charge based on usage — bill per API call, per token, per anything you can count. Learn more about usage-based billing.
  • Seat-based pricing. Sell a number of seats with optional volume tiers, and let the buyer assign them to teammates. Learn more about seat-based billing.
Metered prices stack on top of the others. You can pair one with a fixed base fee for a classic “base + usage” plan, and you can attach multiple metered prices to the same product if you want to bill on more than one dimension at once — say, per API call and per GB of storage. Pricing type is locked in at creation, but for fixed-price products you can change the amount at any time. Existing subscribers are grandfathered onto the price they signed up at, so a price change only affects new purchases. If you do want to migrate someone onto the new price, you can do it per subscription from the dashboard or the API. Tax behavior controls whether Numeral treats a price as tax-inclusive or adds tax on top. The production integration returns tax where the legally liable account has an active registration and records completed sales and adjustments in Numeral. Provider filing and remittance require their own enabled and authorized workflows. See Tax Inclusive Pricing for presentation details and the distinction between the OurPay ledger and provider-backed compliance state.

​
Tax classification

Set a product’s tax_code to what the buyer actually receives. OurPay sends that classification on every non-zero calculation and completed sale; Numeral uses it together with the seller, customer location, tax IDs, and active registrations to determine the result. The default is General SaaS or cloud service for compatibility with existing products. The dashboard supports non-taxable products, personal- and business-use SaaS or downloadable software, digital books, audio, video, live streams, images, newsletters, online community access, gift cards or stored-value credit, payment processing, general services, and consulting services. Choose Non-taxable product or service only when that treatment has been confirmed for the product and jurisdictions involved. A zero-tax sale is still reported to Numeral so nexus and filing records are complete; it is not silently omitted. Changing a product’s classification affects future calculations. It does not rewrite completed orders, refunds, or provider records.

​
Multiple payment currencies

The product catalog can store prices in several currencies. Your organization has a default payment currency that acts as the fallback, and you can add more on top. A price in the default currency is required — if you leave it empty, the product is treated as free. The price structure (price type, metered prices, and so on) must match across every currency you enable. OurPay picks the currency based on the customer’s geolocation at checkout. If their currency isn’t enabled on the product, it falls back to your organization’s default.
The central PayPal integration accepts a checkout only when its currency matches the organization’s Seller Payable ledger currency. New accounts in the standard deployment use USD, so offer USD at checkout until multi-currency ledgers are enabled. Catalog support for another currency does not by itself mean the live PayPal checkout can accept it.
Creating checkout sessions from a backend or proxy? OurPay reads the customer’s geolocation from the IP address of the request that creates the session. If you create sessions server-side (an API, a Cloudflare Worker, etc.), OurPay sees your server’s IP and may pick the wrong currency.Forward the customer’s IP as customer_ip_address when creating the session.
OurPay supports 130+ currencies for product pricing:

​
Trial period

For recurring products, toggle Enable trial period to give customers a window where they aren’t charged. Pick a number and a unit (days, weeks, months, or years) and OurPay handles the rest. Learn more about trials.

​
Metadata

You can attach arbitrary key–value metadata to a product. It’s not shown to customers, but it travels along on every order, subscription, and webhook tied to the product, which makes it useful for keeping track of internal IDs or categories that live outside OurPay.

​
Automated Benefits

Benefits are what your customers actually get when they buy: license keys, Discord roles, GitHub repository access, file downloads, feature flags, or a custom benefit you wire up yourself. OurPay grants and revokes benefits automatically as customers purchase, renew, or cancel. Learn more about benefits.

​
Checkout Page

How your product is represented during checkout.

​
Description

Optional copy that appears on the checkout page. Use it to pitch the product, list what’s included, or anything else that helps the customer commit. Markdown is supported.

​
Product media

Upload images to display on the checkout page. Images can be up to 10MB each, and you can re-arrange or remove them at any time.

​
Checkout fields

Collect extra information from customers at checkout — phone numbers, terms-of-service agreements, custom data you need for fulfillment, anything you want. Fields are defined once at the organization level and then enabled per product, where you also choose whether each one is required. Supported field types: text, number, date, checkbox, and select.
A required checkbox blocks confirmation until the customer ticks it. Handy for legal terms.
The collected values show up on the resulting order or subscription.

​
Update a product

Most things on a product can be edited after the fact, except for the billing cycle and pricing type — those are locked in at creation. To change either, create a new product. A few things to know:
  • Existing subscribers stay on their original price. Changing a fixed price only affects new purchases.
  • Benefit changes propagate. Add a benefit and existing customers get it automatically. Remove one and they lose access.
  • Need a similar product? Use Duplicate Product from the product menu to clone an existing one as a starting point — handy for spinning up a yearly variant of a monthly plan, or for A/B testing pricing.

​
Archive a product

Products can be archived but not permanently deleted. Click Archive from the product menu and the product disappears from new checkouts. Existing customers keep their access, and active subscriptions keep renewing. You can unarchive at any time from the same menu to make the product available again.

​
FAQ

OurPay takes a different approach to what the industry typically calls variants. Each product has a single pricing model, and instead of bolting variants onto one product, you create one product per pricing model and showcase them together at checkout.So a “monthly” and “yearly” plan are two products, each with their own pricing and benefits, presented side-by-side via Checkout Links or the Checkout Session API. It keeps the API and the data model clean, and gives you full freedom over what each option includes.
Yes, for fixed-price products. Existing subscribers are grandfathered onto their original price and only new purchases see the updated amount — but you can move individual subscribers onto the new price per subscription if you want. Billing cycle and pricing type can’t change.
Yes. Set the price type to Metered and link it to a meter that tracks the events you care about. Full walkthrough in the usage-based billing guide.
Yes, via seat-based pricing. The buyer purchases a number of seats and assigns them to teammates, who each get the product’s benefits.
The catalog can select an enabled currency from customer geolocation and fall back to the organization default. In the current central PayPal deployment, however, a paid checkout is accepted only when that currency matches the organization’s Seller Payable ledger currency (USD for standard accounts). See Multiple payment currencies.
Yes. From the product list or the product menu, pick Duplicate Product to clone all the settings into a new draft you can tweak before saving.