Skip to main content
Payments v1

Payments API

M-Pesa and payment intents for checkout flows.

Create payment intents, trigger STK Push, and receive webhook updates. Built for merchants and platforms that need predictable mobile money UX.

  • M-Pesa STK Push and C2B flows
  • Sandbox + production keys
  • Idempotent payment intents
  • Webhook delivery with retries
Open docs Getting started
api.lestertechlabs.com

POST /v1/payments/intents

201 Created

{{ body|default:"{
  \"status\": \"success\",
  \"data\": { ... }
}" }}

Apikey

Auth

1,200/hr

Rate limit

v1

Version

3

Endpoints

Use cases

Where teams use Payments API

Checkout

Collect mobile money at payment time.

Subscriptions

Recurring billing with retry policies.

Disbursements

Payouts to customer wallets (where enabled).

Endpoints

Core surface

Full docs →
POST /v1/payments/intents

Create a payment intent.

GET /v1/payments/intents/{id}

Fetch payment intent status.

POST /v1/payments/webhooks/test

Send a signed test webhook to your endpoint.

Pricing

Plans

Start free in sandbox. Scale when traffic grows.

Sandbox

Free

1,000 requests / month

Growth

USD 49

50,000 requests / month

Scale

USD 199

250,000 requests / month

FAQ

API FAQs

Practical answers before you integrate.

Which payment rails are supported?

M-Pesa is first-class. Card and additional wallets depend on your workspace configuration.

How do webhooks work?

Register an HTTPS endpoint. We sign payloads and retry with backoff on non-2xx responses.

Payments API

Ready to integrate?

Open the docs for endpoint details, or request access and we'll help you go live.

Open docs Getting started
  • Free estimate · reply in 1 business day
  • Production delivery · remote-first
  • M-Pesa, cloud, and AI ready

Next step

Start your project

  1. 1 Tell us about your goals
  2. 2 Get a tailored proposal
  3. 3 Ship with LesterTechLabs
hello@lestertechlabs.com Or visit the contact page