International Gateway

Accept cards from 80+ countries into a Djiboutian balance.

Card-not-present acceptance on top of Cybersource, with 3-D Secure 2, network tokens, Decision Manager risk, and a hosted page that converts. One API, one ledger, one settlement file — same as every other rail.

Get started Read the docs

By the numbers

Schemes: Visa · MC · JCB · UPI · Amex
Currencies: 40+
3DS protocol: EMV 3DS 2.2
Settlement: Daily T+1

Built on Cybersource. Wrapped in MerasPay.

The underlying network is the global scheme rails everyone trusts. The integration on top is the one we want Djiboutian merchants to actually be able to use.

Cards from 80+ countries

Visa, Mastercard, JCB, UnionPay, Amex (via Cybersource). Issuers across MEA, Europe, North America, and APAC, with multi-currency settlement back into a DJF or USD merchant balance.

Native 3-D Secure 2

Frictionless or step-up challenge, EMV 3DS 2.2 protocol, with liability shift on every authentication. We carry the dsTransId through the auth and into the receipt.

Network tokens — not raw PAN

On save-card flows we vault a network token (Visa VTS / Mastercard MDES). Auth uplift averages 2-4pp and the token survives card reissuance.

Decision Manager risk rules

Cybersource Decision Manager scores every auth on 60+ signals. Default rules: AVS, CVN, BIN country, velocity, device fingerprint, IP geo. Override any threshold per merchant.

Drop-in or direct

Use the Hosted Checkout for SAQ-A scope or call PaymentIntents server-to-server with our hosted fields for SAQ-A-EP. Same intent shape, same webhooks, your choice.

Disputes + chargebacks built-in

Cybersource chargeback feed lands as MerasPay dispute objects. Evidence submission, deadlines, win/loss tracking — same machine as every other rail.

The card-not-present payment flow

Server-to-server PaymentIntent, hosted-field tokenization, optional 3DS step-up, capture. Idempotent end-to-end.

1
Create a PaymentIntent
POST /v1/payment_intents with amount, currency (USD / EUR / DJF / etc), payment_method.type = card, and the customer's country if known. Gateway routes to the Cybersource CNP adapter.
2
Tokenize the card
Customer enters card details into a MerasPay hosted field or hosted checkout page. We exchange them for a one-time token; PAN never touches your server. Save-card flow swaps the token for a network token vaulted under the customer.
3
3-D Secure challenge if needed
Issuer decides frictionless or step-up. On step-up we return next_action.type=redirect_to_url; you redirect, customer authenticates, we resume the auth.
4
Capture + settle
Auth approved → capture (immediately or delayed). Cybersource sends the daily settlement file; our reconciler matches it to ledger entries and credits the merchant balance in their preferred currency.

See it in code

A USD 125.00 charge against a tokenized Visa, where the issuer decided to step-up. After the customer authenticates at the redirect_to_url, the intent resumes to succeeded.

http

POST /v1/payment_intents HTTP/1.1
Authorization: Bearer sk_live_...
Idempotency-Key: 9b1d4f0c-7b6f-4e72-a3c2-8aef9d12c0ed
MerasPay-Version: 2026-05-01
Content-Type: application/json

{
  "amount":   12500,           // 125.00 in minor units
  "currency": "USD",
  "payment_method": {
    "type":  "card",
    "card":  { "token": "tok_visa_4242..." }
  },
  "confirm":            true,
  "return_url":         "https://shop.example.com/return",
  "description":        "Order #1024",
  "customer": { "country": "FR" }
}

# Response — issuer required 3DS challenge
{
  "id":     "pi_01HZF...",
  "status": "requires_action",
  "next_action": {
    "type":           "redirect_to_url",
    "redirect_to_url": "https://api.meraspay.io/cards/3ds/ch_abc..."
  },
  "client_secret": "pi_..._secret_..."
}

Frequently asked

Who is my acquirer behind the scenes?▾

MerasPay onboards into a regional Cybersource acquirer that supports settlement into Djibouti. The merchant's legal contract is with MerasPay; the scheme money flows acquirer → MerasPay nostro → merchant balance. Settlement currency is the merchant's choice (DJF or USD by default).

How does pricing compare to building this myself?▾

A direct Cybersource integration assumes you have an acquirer, MOU, PCI compliance, dispute desk, reconciliation engine, and 3DS gateway. We bundle all of that into a single transparent rate card per transaction (interchange + scheme + assessment + our processing margin). For most merchants this is materially cheaper than building.

Does it work for one-off purchases as well as subscriptions?▾

Yes. SetupIntents save a network-token-backed payment method against a customer; Subscriptions charge it on a schedule with smart retries + dunning. Or just call PaymentIntents with confirm=true and an attached payment_method for one-shot.

What happens to declined transactions?▾

You see the same response codes Cybersource sees (we surface ProcessorResponseCode + scheme reason). For soft declines (61, 91) the smart-retry handler retries automatically on dunning runs. For hard declines (14, 41) the customer must update their card.

Do you support remittance origination via cards?▾

Yes — that's the funding-rail half of /products/remittance-origination. Same gateway, classified for the corridor flow with extra AML hooks on the recipient side.

Ready to integrate?

Get a sandbox account in minutes. Production goes live after a brief KYB review.

Get a sandbox account Browse the API reference →