Send local payoutsthrough one integration.

Pementek gives businesses a consistent way to send merchant-approved payouts through supported local wallets, mobile money services and market-specific payout methods.

Create payouts from your backend, track transaction state and receive verified completion updates through the Pementek API and signed webhooks.

API Reference→Contact Pementek

Payout$50.00

Processing

ReferenceWITHDRAWAL-58271

MethodLocal Payment

DeliveryLocal Wallet

Payout createdRequest accepted

ProcessingTransaction in progress

VerificationAwaiting verified result

Local disbursements without a fragmented payout stack

Sending money across local payment ecosystems can require different wallet integrations, operational workflows and transaction handling for each market.

Pementek provides a common payout layer so your application can create and manage supported local payouts through one consistent platform.

Your business remains responsible for deciding whether a withdrawal or disbursement should be approved. Once approved, Pementek handles the payout transaction lifecycle and provides the authoritative transaction result back to your backend.

Infrastructure forreliable local payouts.

Pementek combines payout creation, transaction state, verification and backend notifications through one consistent integration.

Create payouts

Create merchant-approved payout transactions through one consistent server-side API.

Local payout methods

Send money through supported local wallets, mobile money services and market-specific payout methods.

Safe retries

Use idempotency keys to reduce the risk of creating duplicate payout instructions during network retries.

Verified completion

A payout is treated as successful only after Pementek has sufficient verified transaction evidence.

Signed webhooks

Receive authenticated payout updates directly from Pementek to your backend.

Consistent status

Retrieve the current payout state through the API whenever your application needs to reconcile its local state.

From approved withdrawalto verified payout.

Payout processing begins only after your own application has decided that the requested withdrawal or disbursement is valid.

Approve the withdrawal

Your own system validates and approves the customer withdrawal or disbursement before creating a payout.

Create the payout

Your backend sends the payout amount, destination details, market information and merchant reference to Pementek.

Pementek processes the payout

The transaction moves through controlled payout processing using the supported local payout method.

Verify outgoing payment evidence

Pementek verifies supported transaction evidence before declaring that the payout completed successfully.

Receive the final result

Your backend receives a signed webhook event or retrieves the latest payout state through the API.

Create a payoutfrom your backend.

Use an authenticated server-side request and a stable idempotency key for each logical payout operation.

POST /v1/payouts

curl -X POST \
https://api.pementek.com/v1/payouts \
-H "Authorization: Bearer $PEMENTEK_API_KEY" \
-H "Idempotency-Key: withdrawal-58271-payout-1" \
-H "Content-Type: application/json" \
-d '{
  "merchant_reference": "WITHDRAWAL-58271",
  "amount": 50,
  "currency": "USD",
  "country": "US",
  "payment_method": "LOCAL_PAYMENT_METHOD",
  "recipient": {
    "account": "CUSTOMER_ACCOUNT"
  }
}'

Example response

JSON

{
  "id": "po_01JQA8C4M9R2X7N5V1K6T3D8F",
  "merchant_reference": "WITHDRAWAL-58271",
  "amount": 50,
  "currency": "USD",
  "country": "US",
  "payment_method": "LOCAL_PAYMENT_METHOD",
  "status": "CREATED",
  "created_at": "2026-10-09T15:04:28Z"
}

Your application approves the payout first

Pementek should receive a payout request only after your own application has completed the checks required to approve the customer withdrawal or merchant disbursement.

This can include your own account rules, available balance, customer eligibility, fraud controls and any other checks required by your product.

Pementek then processes the approved payout instruction and reports the resulting transaction state.

Avoid duplicate payouts

Duplicate payout creation can result in real financial loss. Network timeouts should therefore never cause your application to immediately create another independent payout request.

Use a stable idempotency key for each logical payout and reuse the same key when safely retrying that same request.

If the outcome of a payout request is uncertain, retrieve the existing payout state before creating another payout for the same customer withdrawal.

Verified completion

A payout request being accepted does not mean that the customer has already received the funds.

Pementek reports final success only after the platform has sufficient supported evidence that the outgoing financial transaction completed successfully.

This verification-first approach helps prevent merchant systems from marking withdrawals as paid based solely on an intermediate application response.

Payout states built forasynchronous processing.

Local payout infrastructure can take time to produce a definitive result. Explicit states allow your backend to distinguish processing from verified completion.

CREATED

The payout has been created and accepted by Pementek.

ROUTING

Pementek is preparing the payout for processing.

WAITING_FOR_PROVIDER

The payout is temporarily waiting for an available processing route.

PROCESSING

The payout is actively progressing through the local payout flow.

VERIFYING

Pementek is verifying outgoing transaction evidence before determining the final result.

PENDING_RECONCILIATION

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

SUCCESS

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

PENDING_RECONCILIATION means a definitive result is not yet available. It should not automatically be treated as payout failure or as confirmed success.

Do not create a second payout while the first is unresolved

Once a payout has entered active processing, your application should continue tracking that transaction rather than creating another payout simply because a final result has not yet arrived.

Use the payout identifier, your merchant reference and the current transaction state to reconcile the original instruction.

This pattern reduces the risk of duplicate money movement when external payment systems respond asynchronously.

Signed payout updates

Important payout state changes can be delivered directly to your backend through signed Pementek webhook events.

Your application should verify the webhook signature and process duplicate event delivery idempotently before updating balances, withdrawal records or customer-facing status.

Read Webhook documentation→

Handle uncertain outcomes safely

Distributed financial systems can occasionally produce delayed or incomplete transaction evidence.

When Pementek cannot yet establish a definitive payout result, the transaction can remain pending for additional reconciliation rather than being incorrectly declared successful or failed.

Your application should continue tracking the existing transaction until an authoritative state is available.

Security for outgoing money movement

Payout operations are designed around authenticated server-side API access, encrypted communication, controlled transaction states and signed event delivery.

Private API credentials should remain inside trusted backend infrastructure and should never be exposed to browsers, customer devices or public source code.

Pementek's transaction verification and reliability controls provide a consistent foundation for processing outgoing financial transactions.

Learn about Security→

Local payout coveragethat keeps expanding.

Pementek supports local money movement across Bangladesh, Pakistan, India, Sri Lanka, Nepal, Kenya, Nigeria, Ghana and Niger, with additional markets and local payment methods being added as coverage expands.

Explore Coverage→

Send local payoutswith Pementek.

Use one consistent integration for merchant-approved local payouts, verified transaction results and signed backend updates.

API Reference→Contact Pementek