Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.chipipay.com/llms.txt

Use this file to discover all available pages before exploring further.

The Bill Payments service is live in Mexico (MXN). Settlement happens in USDC on Starknet — your users hold crypto, your provider gets paid in fiat, you earn a configurable markup on every transaction.

At a glance

700+ services

Live SKUs across all 4 categories

170+ brands

Direct integrations with major Mexican carriers and providers

4 categories

Phone, Gift Cards, Bills, Phone Bundles

Earn a markup

Set your own per-transaction markup; we settle in USDC

What’s in the catalog

35 carriers · 379 servicesTop up prepaid phone balance for any major Mexican carrier. Your users pay in USDC, the carrier sees a normal recharge.

Telcel

Telcel

AT&T

AT&T (Iusacell - Nextel)

Movistar

Movistar

BAIT

BAIT

Mimovil

Mimovil

ULTRACEL

ULTRACEL

Axios Mobile

Axios Mobile

VALOR TELECOM

VALOR TELECOM
…and 27 more carriers (FlashMobile, OUI, RediCoppel, FRC Mobile, ABIB, Beneleit, Megamovil, and others).
curl -G "https://api.chipipay.com/v1/skus" \
  --data-urlencode "category=RECARGAS" \
  --data-urlencode "carrierName=Telcel" \
  --data-urlencode "limit=20" \
  -H "x-api-public-key: $CHIPI_PUBLIC_KEY" \
  -H "x-api-secret-key: $CHIPI_SECRET_KEY"
Response is an array of SKUs ({ id, chipiName, fixedAmount, currency, carrierName, ... }). Pass id to POST /v1/sku-purchases to charge — see the Node guide.
Logos are hot-linked from the production catalog — when admin updates a logo, this page reflects it on the next docs build with no code change. Carrier and SKU counts are a static snapshot taken on 2026-05-07; the live catalog continues to grow.

Pick your stack

Node.js / Server-side

Full purchase flow with @chipi-stack/backend, lifted from the staging smoke test.
Python and React guides land in follow-up PRs.

How it works

  1. Browse the catalog with GET /v1/skus — filter by category + carrierName to find what you need.
  2. Buy with POST /v1/sku-purchases — pass the skuId, the user’s reference (phone number, account, etc.), the amount in MXN, and the user’s gasless wallet. Chipi covers gas; the user’s USDC pays the bill.
  3. Track with GET /v1/sku-purchases/:id — poll until status is SUCCESS.
The full code for steps 1-3 is on the Node guide.

What you charge your users

Set your own markup per transaction in the Dashboard at /configure/skus. We settle the provider in MXN, charge your user in USDC, and credit your service wallet with the spread minus a flat ~$0.001 USDC settlement fee.
Catalog data verified against production at the time this page was generated. Smoke-test attribution: see staging-integration/staging-purchases.test.ts at commit 90c7020.