Quickstart

Use an sk_test_ key on https://buy.api.yabetoopay.com — there is a single host, the key carries the mode. A subscription created in test stays in test for its whole life.

Create a product and its recurring price

A subscription is built on a price of type: "recurring". The cadence is carried by billingInterval and billingIntervalCount.

curl -X POST https://buy.api.yabetoopay.com/v1/prices \
  -H "Authorization: Bearer sk_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "productId": "prod_...",
    "amount": 5000,
    "currency": "xaf",
    "type": "recurring",
    "billingInterval": "month",
    "billingIntervalCount": 1
  }'

The API does not make billingInterval and billingIntervalCount mandatory on a recurring price. Always set them: a recurring price without a cadence creates a subscription that never renews, with no error.

Field details: Prices.

Create the subscription with the customer's Mobile Money number

The customer is found or created by email. Their payment method becomes their default one: it is the one requested at every renewal.

curl -X POST https://buy.api.yabetoopay.com/v1/subscriptions \
  -H "Authorization: Bearer sk_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "customerEmail": "ada@example.com",
    "firstName": "Ada",
    "items": [{ "priceId": "price_...", "quantity": 1 }],
    "paymentMethodData": {
      "type": "momo",
      "momo": { "country": "cg", "msisdn": "242061234567", "operator_name": "mtn" }
    },
    "idempotencyKey": "signup-ada-2026-09"
  }'

The response comes back after the payment request — the call waits for the operator’s answer.

201

{
  "subscription": {
    "id": "sub_...",
    "status": "active",
    "customerEmail": "ada@example.com",
    "currentPeriodStart": "2026-09-17T10:00:00.000Z",
    "currentPeriodEnd": "2026-10-17T10:00:00.000Z",
    "nextBillingDate": "2026-10-17T10:00:00.000Z",
    "items": [{ "id": "si_...", "priceId": "price_...", "quantity": 1 }]
  },
  "paymentStatus": { "success": true, "status": "paid", "requiresAction": false },
  "invoice": { "id": "inv_...", "status": "paid" }
}

If the customer declines or does not answer, the response is still a 201: paymentStatus.success is false and the subscription is unpaid. See Create through the API.

Listen to webhooks

Two events tell the subscription’s story:

Event	When
`subscription.created`	At creation — `data.status` is `active`, `unpaid` or `trialing` depending on the first payment’s outcome
`invoice.paid`	At every settled cycle

The full list: Webhooks.

Simulate the renewal

In test mode, a test clock moves the subscription to its due date without waiting a month.

Lifecycle

The six statuses and their transitions.

Hosted page

Let the customer subscribe on their own.

Billing cycle

What happens at each due date, and when.

API reference

The object and its ten endpoints.

Get started

Create a subscription

Manage

Billing

Resources

Next

Lifecycle

Hosted page

Billing cycle

API reference

​Next

Lifecycle

Hosted page

Billing cycle

API reference

Next