A crypto payment gateway is the bridge between your store and digital payments: the customer pays, you get paid — no card terminal and no bank in the middle. With the DePix App, you accept Pix and crypto on your website in two ways, from the simplest to the most advanced: a “Pay” button that sends the customer to a ready-made payment page (no coding) or a full integration via API and webhooks — the DePix App API documentation has the complete reference.

Either way, the customer pays with an ordinary Pix (Brazil’s instant payment system), from their own banking app, without knowing what crypto is. You receive the amount in DePix — the stablecoin pegged to the Brazilian real (1 DePix = 1 real) on the Liquid Network — straight into your non-custodial integrated wallet, with privacy and control. Here are both paths, step by step.

Part 1: the “Pay” button with redirect (no developer needed)

If you are not a programmer — or you want the fastest possible integration — start here. The idea is simple: when the customer clicks “Pay” on your site, they go to a payment page hosted by the DePix App (at pay.depixapp.com), pay with Pix there, and when they are done they are sent back to your site through the redirect_url field. You do not design a payment page, generate a QR code, or deal with the Pix protocol — it all comes ready.

A practical example: the “Pay with Pix” button on your site

Say you sell a t-shirt for R$ 29.90. On your site — whether it is WordPress/WooCommerce, Wix, Nuvemshop, Loja Integrada or even a link in your Instagram bio — you add a “Pay with Pix” button. There are two levels, from the easiest to the most flexible.

1. No code (what most merchants do). Create a payment link or register a product in the app — each product gets a permanent link in the format pay.depixapp.com/your-store/t-shirt (see the payment links and checkout page guide). Then just use that link as the destination of a button. In WordPress, for example, add a Custom HTML block with:

<a href="https://pay.depixapp.com/your-store/t-shirt">Pay with Pix</a>

It works on any platform — WooCommerce, Wix, Nuvemshop, Loja Integrada, Linktree: just paste the link into the button. This path covers the vast majority of merchants, with no programming at all.

2. With a dynamic amount (one server call). When the amount changes per order — a cart with several items, for instance — your site creates the checkout on the fly and redirects the customer. It is a single call, which we cover next.

How to create the checkout and redirect the customer

Under the hood, creating a dynamic charge is a single call. When the customer clicks “Pay”, your server sends a POST to /api/checkouts with the purchase amount (always in cents), a description, and — the key part — the redirect_url the customer should return to after paying. The response includes a payment_url field: that is where you redirect the customer.

Here is the minimal curl call:

curl -X POST https://depix-backend.vercel.app/api/checkouts \
  -H "Authorization: Bearer sk_live_<your-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 2990,
    "description": "T-shirt size M",
    "redirect_url": "https://my-store.com/thank-you"
  }'

The value 2990 represents R$ 29.90 — remember amounts are always in cents. The response arrives with status 201 Created:

{
  "id": "chk_01jxxxxxxxxxxxxxxxxxxxxxx",
  "status": "pending",
  "amount": 2990,
  "payment_url": "https://pay.depixapp.com/chk_01jxxxxxxxxxxxxxxxxxxxxxx",
  "pix": {
    "qr_code": "00020126580014br.gov.bcb.pix..."
  }
}

Take the payment_url and redirect the customer’s browser to it. In any server language this is a simple HTTP 302 redirect. The customer sees the DePix App payment page, scans the QR code or copies the Pix code in their banking app, pays, and is sent back to your redirect_url — in the example, https://my-store.com/thank-you. That’s it: you accepted Pix on your site without building anything from scratch.

Part 2: full integration via API and webhooks

Part 1 already solves most cases. But if you run a store with orders, inventory, and automatic fulfillment, you will want to confirm the payment programmatically — without relying on the customer returning to the thank-you page. This is where API keys and webhooks come in.

The DePix App API uses a key in the Authorization header on every authenticated request, in the format Bearer sk_live_<your-key>. There are two types of key¹:

  • sk_test_ — test keys, released automatically when you create your merchant account. No real money moves. Use them to integrate against the sandbox.
  • sk_live_ — production keys, which move real money. They require manual approval: in the API Keys area, click “Request access”, answer a few short questions about your integration, and the team reviews it.

Keep the key safe — it is shown only once, at creation. The base URL for all endpoints is https://depix-backend.vercel.app, and all monetary values are integers in cents.

Confirming payments with webhooks

When a checkout’s status changes, the API sends a POST to the callback_url you provided at creation. This is the robust way to know the payment landed: instead of polling the API, you are notified automatically. Just include the callback_url field when creating the checkout:

{
  "amount": 2990,
  "description": "T-shirt size M",
  "callback_url": "https://my-store.com/webhook/depix",
  "redirect_url": "https://my-store.com/thank-you",
  "metadata": { "order_id": "ORD-123" }
}

The metadata field carries data from your system (like order_id) and comes back intact in every webhook — ideal for tying the payment to the right order. The main events are checkout.processing (Pix received, converting) and checkout.completed (payment confirmed, DePix in the merchant’s wallet). There are also checkout.cancelled and checkout.expired².

Two essential security and reliability practices:

  • Validate the signature. Each webhook carries an X-DePix-Signature header (HMAC-SHA256). Always verify the signature before processing — that guarantees the request really came from the DePix App.
  • Be idempotent. Delivery is “at-least-once”: the same event may arrive more than once. Use the X-DePix-Event-Id header (stable across retries) to deduplicate and never fulfill an order twice.

Testing everything in the sandbox before going live

Never take a payments integration to production without testing it. With an sk_test_ key, you create test checkouts isolated from real ones: the is_live field returns false and the generated QR code is not a valid Pix. To simulate the money landing, call the simulation endpoint:

curl -X POST \
  https://depix-backend.vercel.app/api/checkouts/chk_01jxxxxxxxxxxxxxxxxxxxxxx/simulate-payment \
  -H "Authorization: Bearer sk_test_<your-key>"

This marks the test checkout as paid and fires the checkout.completed webhook exactly as in a real payment — perfect for validating your integration end to end. Only after everything works in the sandbox, swap the sk_test_ key for the sk_live_ one and you are live.

Why use the DePix App as a crypto payment gateway

Using the DePix App as a crypto payment gateway goes beyond technical convenience. Every incoming payment becomes DePix in your integrated wallet — a non-custodial wallet where the keys stay on your device and the app never holds your funds. You keep control and privacy over what you receive, with no card terminal, no mandatory business registration, and no 30-day settlement delays.

The processing fee is 2% + R$ 0.99 per payment received³, competitive with debit card rates — and without the hardware cost. The minimum per checkout is R$ 5.00. It is worth remembering the security context: deposits go through an anti-fraud window of up to 24 hours (D+1) before the DePix reaches the wallet, a protection against Pix scams. For everyday sales, this model combines the best of both worlds: the familiarity of Pix for the customer and the sovereignty of crypto for you.

And remember the role of each asset: DePix is money to spend and receive with privacy, not a store of value. If the goal is to save long term, Bitcoin (or L-BTC, its version on Liquid) is the right tool — and you can convert DePix into those assets straight from the integrated wallet whenever you want.

References

  1. DePix App — API documentation: authentication and checkouts
  2. DePix App — Webhooks and checkout events
  3. Central Bank of Brazil — Pix: what it is and how it works

Your store, your rules, your privacy

Pix has convenience — DePix has privacy and control. Accept payments on your website without exposing every sale to the banking system, and get paid in digital money only you control. Get started at depixapp.com.