merebpay
  • Platform
  • Developers
  • Pricing
  • Blog
  • Docs
Sign In
Get Started

Getting started

Authentication

How API keys, environments, and request signing work.

Getting started

  • Quickstart
  • Authentication

Core APIs

  • Payments API
  • Payouts API

Platform

  • Webhooks
  • Errors

Every request is authenticated with a secret key sent as a Bearer token. Sandbox keys start with mk_test_, live keys with mk_live_ — they are never interchangeable.

Example request

cURL
curl https://api.merebpay.com/v1/charges \
-H "Authorization: Bearer mk_test_..." \
-H "Content-Type: application/json"

Best practices

Keep secret keys server-side only. Use publishable keys for anything that runs in a browser or mobile app.

  • Rotate keys from Developers → API Keys if one is ever exposed
  • Use a separate sandbox key per environment (local, staging, CI)
  • Never commit a live key to source control
PreviousQuickstartNextPayments API

On this page

  • Example request
  • Best practices
Mereb

Modern transaction architecture enabling African tech hubs to grow, scale, and settle seamlessly.

Product

  • Services
  • Payment Links
  • Security
  • Pricing

Company

  • About Mereb
  • Careers
  • Newsroom
  • Contact

Resources

  • Documentation
  • System Status
  • Support Hub
  • FAQ

Legal

  • Privacy Policy
  • Terms of Use
  • Regulatory Disclosures

Mereb © 2026. Built in Africa for the world.

XIGINFB