Accept local paymentsthrough one API.

Pementek Payment API gives your backend one consistent interface for creating and managing local payment transactions across supported markets.

Connect customers to local wallets, mobile money and market-specific payment methods while Pementek provides the transaction lifecycle, verification and server-to-server payment updates behind the experience.

API Reference→Documentation

APIREST / v1

RetriesIdempotent

EventsSigned Webhooks

ProcessingServer-side

MarketsGrowing Coverage

A consistent payment layer for local methods

Local payment infrastructure can vary significantly by country. Customers may use mobile wallets, mobile money services or other payment methods that operate differently from traditional card-based payment systems.

Pementek provides a unified payment API so merchants can work with supported local payment methods through a consistent transaction model instead of building a completely different payment backend for every market.

Your system creates the payment, Pementek manages the transaction lifecycle, and your backend receives the authoritative result through the API and signed webhooks.

Everything needed toprocess local payments.

The Payment API combines transaction creation, verification, status management and merchant notifications behind one integration.

Create payments

Create local payment transactions through one consistent server-side API.

Local payment methods

Present supported wallets, mobile money and market-specific payment methods to customers.

Safe retries

Use idempotency keys to safely retry supported requests without unintended duplicate payment creation.

Verified results

Use authoritative transaction states and verified server-side results instead of relying on customer-side confirmation.

Signed webhooks

Receive authenticated transaction updates directly from Pementek to your backend.

Status retrieval

Retrieve the latest transaction state whenever your application needs to reconcile its local state.

How a payment works

A Pementek payment begins with a server-side API request from your application and continues through a controlled transaction lifecycle until a definitive result is available.

Create the payment

Your backend sends the amount, currency, country, payment method and your own merchant reference to the Pementek API.

Present the payment experience

The customer completes the payment using the supported local payment method available for the transaction.

Verify the transaction

Pementek processes available transaction evidence and determines whether the payment can be safely confirmed.

Receive the result

Your backend receives signed webhook events or retrieves the latest transaction state through the API.

Create a paymentwith one request.

Payment creation uses an authenticated server-side request together with a unique merchant reference and idempotency key.

POST /v1/payments

curl -X POST \
https://api.pementek.com/v1/payments \
-H "Authorization: Bearer $PEMENTEK_API_KEY" \
-H "Idempotency-Key: order-847291-payment-1" \
-H "Content-Type: application/json" \
-d '{
  "merchant_reference": "ORDER-847291",
  "amount": 50,
  "currency": "USD",
  "country": "US",
  "payment_method": "LOCAL_PAYMENT_METHOD"
}'

Example response

JSON

{
  "id": "pay_01JQ9AK8P6V4R2T7X5M3N1C9D",
  "merchant_reference": "ORDER-847291",
  "amount": 50,
  "currency": "USD",
  "country": "US",
  "payment_method": "LOCAL_PAYMENT_METHOD",
  "status": "CREATED",
  "created_at": "2026-10-09T14:32:11Z"
}

Safe retries with idempotency

Network interruptions and request timeouts can happen during payment creation. Your application should not automatically create another financial transaction simply because the first response was not received.

Pementek supports idempotency keys for supported payment creation requests so the same logical request can be retried safely.

When retrying the same logical payment request, reuse the same Idempotency-Key. Do not generate a new key merely because the previous API response was lost.

Transaction states designed forreal payment conditions.

Local payment processing can be asynchronous. Pementek uses explicit transaction states so your application can distinguish active processing from final results.

CREATED

The payment has been created and accepted by Pementek.

ROUTING

Pementek is preparing the payment for processing.

WAITING_FOR_PROVIDER

The payment is temporarily waiting for an available transaction route.

VERIFYING

Pementek is verifying transaction evidence before determining the result.

PENDING_RECONCILIATION

The transaction does not yet have sufficient definitive evidence for a final result.

SUCCESS

The payment has been verified successfully and reached its final successful state.

PENDING_RECONCILIATION is not an automatic failure. It means that Pementek does not yet have enough definitive evidence to declare a final result.

Verification-first payment processing

Pementek does not treat a customer button press, browser redirect or other customer-side indication as independent proof that money was successfully received.

The platform determines transaction results through server-side processing and supported transaction evidence. A successful payment is reported only when the transaction has satisfied the conditions required for confirmation.

This model helps merchants avoid fulfillment based on untrusted or incomplete customer-side signals.

Signed transaction updates

Pementek can notify your backend when important payment state changes occur through signed server-to-server webhooks.

Your system should verify each webhook signature before processing the event and should handle duplicate delivery idempotently.

Browser redirects can still be useful for customer experience, but they should not be used as the final authoritative source of payment status.

Read Webhook documentation→

Local coverage that keeps growing

Pementek currently provides local payment infrastructure across Bangladesh, Pakistan, India, Sri Lanka, Nepal, Kenya, Nigeria, Ghana and Niger.

Additional countries and supported local payment methods can be added over time while merchants continue to use the same core Pementek integration.

Explore Coverage→

Security built into the payment flow

Pementek is designed around authenticated API access, encrypted communication, controlled transaction states and signed event delivery.

Merchant API credentials should remain on trusted server-side systems and should never be exposed in browser JavaScript, public source code or other client-controlled environments.

These controls work together to provide a secure and predictable foundation for payment processing.

Learn about Security→

Build local paymentswith Pementek.

Integrate once and connect your product to supported local payment methods through a consistent payment API.

API Reference→Contact Pementek