Developers

A payments API developers actually enjoy

Clean REST endpoints, predictable objects, signed webhooks and a full sandbox. Integrate cards, ACH and disputes in days, not months.

Get Started Talk to Sales
quickstart.js
import Bear from "bearmerchant";
const bm = Bear(process.env.BM_SECRET_KEY);

const charge = await bm.charges.create({
  amount: 4280,
  currency: "usd",
  source: "tok_visa",
  metadata: { order: "10842" }
}, { idempotencyKey: "a1b2c3" });

// charge.status → "succeeded"
Wait Time: 1 Minute Available: 8 Agents

Get Started Today

Set up your account in 60 seconds.

Overview

Designed for the way engineers really build

Great payment infrastructure disappears into your application. That only happens when the API is consistent, well-documented and safe to retry — and when you can test everything before touching real money.

Bear Merchant is resource-oriented and idempotent by design. Objects behave predictably, errors are descriptive, webhooks are signed, and the sandbox mirrors production so you ship with confidence.

Resource-oriented REST + JSON Idempotent write requests Signed, retried webhooks SDKs for 5 languages Full-fidelity sandbox
Features

Everything in the developer toolbox

From first call to production-grade integration.

REST API

Predictable resources for charges, customers, payouts, disputes and more.

Webhooks

Signed events with automatic retries and a replay tool for debugging.

SDKs

Node, Python, PHP, Ruby and Go libraries kept in lockstep with the API.

Sandbox

Simulate cards, ACH, 3-D Secure and disputes without real funds.

Authentication

Scoped keys and OAuth for platforms and connected accounts.

Documentation

Guides, references and copy-paste recipes for common flows.

Libraries & tooling

Official SDKs, plus the plumbing around them

Every SDK is generated from the same OpenAPI spec, so the docs and the client never drift apart.

PHP Node.js Python Java Ruby Go .NET iOS & Android OpenAPI spec Postman collection CLI Signed webhooks

Sandbox keys are issued instantly and mirror production behaviour, including failure modes.

How It Works

From zero to first charge

  1. 1

    Get keys

    Create a sandbox account and copy your API keys.

  2. 2

    Install an SDK

    Add the library for your language, or call the REST API directly.

  3. 3

    Make a call

    Create a test charge and listen for the webhook.

  4. 4

    Go live

    Swap in live keys and monitor with logs and dashboards.

Benefits

Ship faster and sleep better

Fast integration

Sensible defaults and SDKs get you to a working charge quickly.

Safe retries

Idempotency keys prevent duplicate charges under failure.

Easy debugging

Rich errors, request logs and webhook replay speed up development.

Built to scale

The same API powers a first sale and millions of transactions.

Results that compound

0ms
Median latency
0
Official SDKs
0%
API uptime
0%
Sandbox parity
Who It's For

Who builds on Bear Merchant

SaaS platforms

Embedding payments and payouts for their own users.

Ecommerce teams

Custom checkouts that need control and reliability.

Marketplaces

Splitting payments across many connected accounts.

Fintechs

Building financial products on compliant rails.

Digital products

Fast-moving teams shipping global checkout.

Enterprises

Engineering orgs standardizing on one payments layer.

FAQ

Frequently asked questions

Still unsure about something? Our team answers in plain language — no sales script.

Ask a question

Bear Merchant exposes a resource-oriented REST API that returns predictable JSON. Requests are made over HTTPS and support idempotency keys for safe retries.

Official SDKs are available for Node.js, Python, PHP, Ruby and Go, with community libraries for other stacks. All wrap the same REST API.

We send signed HTTP POST events for things like successful charges, disputes and settlements. Signatures let you verify authenticity, and we automatically retry failed deliveries.

Yes. The sandbox mirrors production and lets you simulate cards, ACH, 3-D Secure, disputes and edge cases without moving real money.

Use scoped secret API keys for server-side calls, publishable keys for client-side tokenization, and OAuth for platforms acting on behalf of connected accounts.

Yes. Send an idempotency key with write requests so retries never create duplicate charges, even across network failures.

Start building today

Create a sandbox account, grab your keys and make your first API call in minutes.

Get API Keys Explore the API