01
Pementek-hosted
Send customers to a payment experience hosted and maintained by Pementek.
A hosted checkout forlocal payments.
Pementek Hosted Checkout gives your customers a secure payment experience for supported local wallets, mobile money and market-specific payment methods without requiring you to build the entire payment interface yourself.
Create the transaction from your backend, send the customer to Hosted Checkout and receive the authoritative payment result through the Pementek API and signed webhooks.
P
Complete payment
$50.00
Order #847291
Local PaymentRecommended
✓
Mobile WalletAvailable
Secure payment powered by Pementek
Launch a local payment experience faster
Building a payment interface for multiple local payment methods can require different instructions, customer journeys and transaction states for each market.
Hosted Checkout gives you a Pementek-managed payment interface while your application continues to control order creation, transaction references and backend fulfillment logic.
This allows your customer experience to remain simple while your payment backend continues to use the same Pementek transaction infrastructure.
Checkout designed forlocal payment flows.
Pementek handles the hosted payment interface while your backend remains in control of the merchant-side transaction lifecycle.
02
Local payment methods
Present supported wallets, mobile money and market-specific payment options appropriate to the transaction.
03
Mobile responsive
Checkout is designed to work cleanly across mobile phones, tablets and desktop browsers.
04
Secure payment flow
Payment creation and final transaction status remain controlled through server-side Pementek processing.
05
Signed webhooks
Receive authenticated transaction updates independently of the customer browser session.
06
Consistent integration
Use the same Pementek integration as your payment coverage expands into additional supported markets.
From your applicationto verified payment.
The browser experience is only one part of the payment flow. Your backend and Pementek remain responsible for the authoritative transaction state.
01
Create a payment
Your backend creates the payment through the Pementek API using the amount, currency, country and merchant reference.
02
Open Hosted Checkout
Redirect the customer to the Pementek-hosted payment experience associated with the transaction.
03
Customer pays locally
The customer follows the available local payment method instructions and completes the payment flow.
04
Pementek verifies
Pementek verifies supported transaction evidence before determining the authoritative payment result.
05
Your backend receives the result
Use signed webhooks or the Payment API to obtain the latest authoritative transaction status.
Create the transactionfrom your backend.
Hosted Checkout starts with an authenticated server-side payment request.
Create payment
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"
}'Checkout response
JSON
{
"id": "pay_01JQ9AK8P6V4R2T7X5M3N1C9D",
"merchant_reference": "ORDER-847291",
"status": "CREATED",
"checkout_url": "https://pay.pementek.com/checkout/pay_01JQ9AK8P6V4R2T7X5M3N1C9D"
}Designed for mobile-first payment markets
Many local payment methods are used primarily from mobile devices. Hosted Checkout is designed to remain clear, responsive and easy to follow on smaller screens.
The checkout experience can present the payment instructions and options relevant to the transaction without requiring your product team to maintain a separate payment interface for every supported method.
Customer redirects are not payment proof
After a customer completes the checkout experience, your application may redirect them back to your website or application.
That redirect is useful for customer experience, but it should not be treated as authoritative confirmation that the transaction succeeded.
Use signed Pementek webhooks or retrieve the current transaction through the Payment API before fulfilling an order or treating the payment as finally successful.
Verified transaction results
Pementek determines payment success through server-side transaction processing and supported transaction evidence.
A customer pressing a button or reaching a confirmation screen does not independently establish that money was received.
If a definitive result is not yet available, the transaction can remain in an intermediate verification or reconciliation state until sufficient evidence exists.
Signed webhooks for backend updates
Hosted Checkout works independently of your customer's browser session. Important transaction changes can be delivered directly to your backend through signed Pementek webhooks.
Your application should verify webhook signatures and process duplicate deliveries idempotently before changing order or fulfillment state.
Read Webhook documentation→Secure by design
Payment creation occurs through authenticated server-side API requests, while protected communication and signed events help maintain transaction integrity between Pementek and merchant systems.
API credentials should remain in your trusted backend environment and should never be embedded in the customer checkout page or other frontend applications.
Learn about Security→One checkout.Growing local coverage.
Pementek supports local payment infrastructure across Bangladesh, Pakistan, India, Sri Lanka, Nepal, Kenya, Nigeria, Ghana and Niger, with additional countries and payment methods being added as coverage expands.
Launch local paymentswith Hosted Checkout.
Create the transaction from your backend and let Pementek provide the customer-facing local payment experience.