Skip to content

Add payments to your app with one API

Charge for apps, licenses, and API access through a single API. Customers pay by card or crypto on a hosted checkout, and your server hears about it right away.

Start accepting payments

Talk to our payments team

Monthly processing volume

What you're interested in

Payment types to enable

or create a business account

  • Retried until accepted

    Webhooks are retried if your server doesn't accept them, so a deploy or a brief outage doesn't drop a paid order.

  • Checkout already translated

    Hosted checkout appears in each customer's language, so you don't build or translate a payment page yourself.

  • Revenue in your own wallet

    Payments go straight to your self-custody wallet, with no reserves, rolling holds, or payout schedule.

Create, redirect, get notified

Create a checkout, send your customer to it, and hear when they've paid.

Create a checkoutPOST /api/v1/payments
AAcme EditorFree plan

Upgrade to Pro

One license, yours to keep.

  • Unlimited projects
  • Export to every format
  • Every update this year
$49.00One-time license
Buy license

Signed webhooks

Verify each event came from 402pay before you act on it.

POSTexample.com/webhooks/402pay
webhook-idevt_3a9c51e2-8d4f-4b07-a6e1-9f2c7b5d0e48
webhook-timestamp1792617240
webhook-signaturev1,K5oZfzN95Z9UVu1EsfQmXbH2c8Rr4tYw0aLpJdE3s6g=
{  "type": "payment.succeeded",  "subject": { "id": "pmt_7c2e9a41-3f6b-4d18-9e05-b81f4c6d2a73"}
Received
AAcme EditorLicenses
JO[email protected]Pro licenseNot active

Any language, or a link

Call the API from any stack, or share a payment link with no code.

Node.jsPythonPHPRubyPayment linkLink
const res = await fetch(`${api}/payments`, {  method: "POST",  headers: {    Authorization: `Bearer ${key}`,    "Content-Type": "application/json",  },  body: JSON.stringify({    amount: "49.00",    description: "Pro license",  }),});const { url } = await res.json();
201urlcheckout.402pay.co/checkout/r4vq8nzt2l

How it works

Every payment takes the same path: paid at checkout, confirmed by a signed webhook, and in your wallet the moment it lands. Your system takes it from there.

  1. Step 1

    Your app creates checkout

    Card, Apple Pay, Google Pay, or crypto, in one hosted checkout.

  2. Step 2

    Card or crypto checkout

    Card, Apple Pay, Google Pay, or crypto, in one hosted checkout.

  3. Step 3

    Signed webhook arrives

    Signed so your server can verify it, and retried if it isn't acknowledged.

  4. Step 4

    License activated

    You fulfill the order, with the funds already in your wallet.

Card processing

Card payments
  • Major cards and wallets

    VisaMastercardAmerican ExpressApple PayGoogle PayVisa, Mastercard, American Express, Apple Pay, and Google Pay, offered alongside crypto in a single checkout.
  • 4% + 30¢

    Per card transaction, with Apple Pay and Google Pay included and no setup or monthly fee. Any provider fee is shown to the customer before they pay.
  • Settled in crypto

    The card provider converts each payment and delivers it to your own wallet in crypto, with no payout in between.
  • Card data stays off your servers

    Customers enter their card details on the card provider's secure page, never on your systems or ours.
  • Routed across providers

    Each payment goes to a card provider that serves the customer's country and amount. If a card is declined, they can try another provider or pay in crypto without leaving checkout.
  • No merchant account

    Cards are on for every business from the start, with no card underwriting, reserve, or rolling hold to apply for.

402pay compared with a traditional processor

Who holds the money
A traditional processorThe processor, until it pays you out
402payYou, in a self-custody wallet
Reserves and rolling holds
A traditional processorCommon on high-risk accounts
402payNone, on cards or crypto
Approval for cards
A traditional processorUnderwriting for a high-risk merchant account
402payNone. Cards are on from the start
Frozen balances
A traditional processorPossible during a review or a closure
402payNo balance on our side to freeze
When the money is yours
A traditional processorOn the processor's payout schedule
402payAs soon as the payment confirms
Ways to pay
A traditional processorMostly cards
402payCards, Apple Pay, and Google Pay routed across card providers, crypto, and payment apps
Start accepting payments
Talk to sales about software developers

Payments for software developers

Why do independent software sellers get payment holds?

Independent software sellers get holds because a new account with sudden sales, customers in many countries, and digital goods with no shipping record all look risky to a processor's review team. Some processors also limit which countries a seller can sign up from, and a license key bought with a stolen card can be disputed long after the key was used. Holds and rolling reserves then delay revenue the business has already earned. With us, payments go straight to your self-custody wallet, with no balance on our side and no payout schedule.

How do I add card and crypto payments to an app with an API?

You add payments by creating a checkout through the API, redirecting the customer to it, and listening for a signed payment.succeeded webhook. The hosted checkout takes Visa, Mastercard, American Express, Apple Pay, Google Pay, and crypto, so you don't build a payment form or handle card details, which are entered on a card provider's secure page. Verify the webhook signature, then activate the license, credits, or API access. A declined card can retry with another provider or switch to crypto, so fewer customers drop out at the last step.

What does a developer handle when selling software and API access?

A developer handles its own terms, license enforcement, taxes, and refunds. Each checkout is a one-time payment, so sell licenses, credit packs, or prepaid usage, and track what each customer has left in your own system. Refunds are sent from your own wallet, and every transfer out needs your password. A card payment can be disputed by the cardholder, while a confirmed crypto payment is final. To start, create a payment link in the dashboard with no code, then move to the API and run a checkout yourself before you launch.

Frequently asked questions

  • Each checkout is a one-time payment, so sell licenses, credit packs, or prepaid usage, and create a new checkout when a customer buys more.
  • Checkout asks for exactly what's left, so you don't write your own logic for partial payments. Each checkout also has its own address and a rate locked while the customer pays.
  • Any stack that can send HTTPS requests and verify a webhook signature works with the API. The developer docs walk through creating checkouts and checking signatures.
  • No. Customers can pay by Visa, Mastercard, American Express, Apple Pay, or Google Pay on a card provider's secure page, and each card payment arrives in your wallet in crypto.
  • No. Every payment settles directly to a self-custody wallet only your business holds the keys to. There's no balance to freeze, no reserve, and no payout schedule.
  • No. 402pay routes each card, Apple Pay, and Google Pay payment to a card provider that serves the customer's country and amount, and the provider delivers it to your wallet in crypto. There's no card underwriting, reserve, or rolling hold.
  • Nothing during the public beta. The pricing page lists every fee that follows, with nothing taken out of a payment.

If you're looking for card-to-crypto payments, there is no alternative.