KBZ Pay
KBZ Pay is KBZ Bank's mobile wallet: customers pay in the KBZ Pay PWA, by scanning a QR code, or from your mobile app.
| Call | What it does | Returns |
|---|---|---|
$kbzPay->pwa($data) | Redirect to the KBZ Pay PWA | RedirectPayment |
$kbzPay->qr($data) | Customer scans a QR | QrPayment |
$kbzPay->app($data) | Your mobile app opens the KBZ Pay SDK | AppPayment |
$kbzPay->status($orderId) | Query an order | PaymentStatusResult |
$kbzPay->handleCallback($request) | Verify the notification | PaymentCallback |
Responses shows what KBZ Pay puts in each result.
How it works
Every KBZ Pay flow starts with the same precreate call and ends with KBZ's signed notification.
Initiating a Payment
use Laranex\PhpMyanmarPayments\KbzPay\KbzPay;
use Laranex\PhpMyanmarPayments\KbzPay\KbzPayConfig;
use Laranex\PhpMyanmarPayments\KbzPay\KbzPayPaymentData;
$kbzPay = new KbzPay(new KbzPayConfig(
appId: '...',
appKey: '...',
merchantCode: '...',
timeoutSeconds: 30,
));
$data = new KbzPayPaymentData(
orderId: 'ORDER_'.$order->id,
amount: 10000,
callbackUrl: 'https://shop.test/payments/kbz/callback',
);
// PWA: send the customer to the KBZ Pay PWA
$payment = $kbzPay->pwa($data);
header('Location: '.$payment->url);
exit;
// QR: encode $payment->qrString into a QR image
$payment = $kbzPay->qr($data);
// In-app: hand the signed values to your mobile app
$payment = $kbzPay->app($data);
header('Content-Type: application/json');
echo json_encode($payment->toArray());KbzPayPaymentData
| Parameter | Type | Required | Rules |
|---|---|---|---|
orderId | string | Yes | Unique per order. Letters, digits and _ only, at most 40 characters |
amount | Amount|int | Yes | Kyat, greater than 0, at most 2 decimal places, e.g. 10000 or Amount::parse('1000.50'). KBZ only accepts MMK |
callbackUrl | string | Yes | Public URL KBZ posts the result to. Absolute http or https URL, at most 512 characters, no query string |
title | ?string | No | Product name shown to the customer |
timeoutMinutes | ?int | No | An integer from 1 to 120. null leaves it to KBZ (120) |
callbackInfo | ?string | No | Free text echoed back in the callback, at most 512 characters once URL-encoded |
PWA Notes
- The PWA only opens on a phone with the KBZ Pay app installed.
- KBZ checks the redirect's
Refereragainst the URL registered with them (errorAOP08512). Redirect from that domain and don't strip the referrer. - After payment, KBZ sends the customer to the return URL registered with them during onboarding; it cannot be set per payment.
Handling Callbacks
KBZ Pay posts JSON nested under a Request key; build the CallbackRequest from the whole request.
// POST /payments/kbz/callback
use Laranex\PhpMyanmarPayments\Exceptions\SignatureVerificationException;
use Laranex\PhpMyanmarPayments\Http\CallbackRequest;
try {
$callback = $kbzPay->handleCallback(CallbackRequest::fromGlobals());
} catch (SignatureVerificationException) {
http_response_code(400);
echo 'invalid callback';
exit;
}
if ($callback->isSuccessful()) {
// $callback->orderId is your merch_order_id
// $callback->gatewayReference is KBZ's mm_order_id
}
$callback->acknowledgement->send(); // plain-text "success"KBZ requires an HTTP 200 with the plain-text body success, answered within about 10 seconds. Otherwise it retries after 60 and 600 seconds; when no callback arrives, query the order.
Status Checks
$result = $kbzPay->status('ORDER_'.$order->id);
if ($result->isSuccessful()) {
// $result->gatewayReference is KBZ's mm_order_id
}status() takes your orderId. An order KBZ doesn't know throws ApiException.
Responses
What KBZ Pay puts in each property. See Results and PaymentCallback & Status for the full classes. A property the gateway didn't send is null. raw holds plain PHP values (JSON numbers stay strings with their exact text), while the typed properties such as amount keep the exact text KBZ sent.
pwa() → RedirectPayment
| Property / Method | KBZ Pay value |
|---|---|
flow() | PaymentFlow::Redirect |
orderId | Your $data->orderId |
url | {pwaUrl}?appid=…&merch_code=…&nonce_str=…&prepay_id=…×tamp=…&sign=… |
gatewayReference | KBZ prepay_id. Always set |
raw | The precreate response: result, code, msg, merch_order_id, prepay_id, nonce_str, sign_type, sign |
qr() → QrPayment
| Property / Method | KBZ Pay value |
|---|---|
flow() | PaymentFlow::Qr |
orderId | Your $data->orderId |
qrString | KBZ qrCode, a payload to encode into a QR image. Always set |
qrImage | Always null |
expiresAt | Now + timeoutMinutes. null when timeoutMinutes is null (KBZ then allows 120 minutes) |
reference | KBZ prepay_id. Always set |
raw | The precreate response, as for pwa() plus qrCode |
qrImageDataUri() | Always null, as qrImage is |
app() → AppPayment
| Property / Method | KBZ Pay value |
|---|---|
flow() | PaymentFlow::App |
orderId | Your $data->orderId |
orderInfo | appid=…&merch_code=…&nonce_str=…&prepay_id=…×tamp=… |
sign | SHA-256 signature of orderInfo, uppercase hex. See Signing |
signType | SHA256 |
raw | The precreate response, as for pwa() |
toArray() | orderId, orderInfo, sign and signType, without raw |
status() → PaymentStatusResult
| Property | KBZ Pay value |
|---|---|
orderId | KBZ merch_order_id, falling back to the orderId you passed. Always set |
status | trade_status mapped, see Statuses |
gatewayStatus | KBZ trade_status, trimmed, e.g. PAY_SUCCESS |
gatewayReference | KBZ mm_order_id. null until KBZ has created the payment |
amount | KBZ total_amount, e.g. 10000 |
raw | The queryorder response: result, code, msg, merch_order_id, mm_order_id, total_amount, trans_currency, trade_status, trans_end_time, nonce_str, sign_type, sign |
handleCallback() → PaymentCallback
| Property / Method | KBZ Pay value |
|---|---|
orderId | KBZ merch_order_id (your orderId) |
status | trade_status mapped, see Statuses |
gatewayStatus | KBZ trade_status, trimmed, e.g. PAY_SUCCESS |
gatewayReference | KBZ mm_order_id |
amount | KBZ total_amount, e.g. 10000 |
raw | The verified Request: appid, notify_time, merch_code, merch_order_id, mm_order_id, total_amount, trans_currency, trade_status, trans_end_time, callback_info, nonce_str, sign_type, sign |
acknowledgement | HTTP 200, body success, Content-Type: text/plain |
Statuses
KBZ trade_status | PaymentStatus |
|---|---|
PAY_SUCCESS | Successful |
WAIT_PAY, PAYING | Pending |
PAY_FAILED | Failed |
ORDER_CLOSED | Canceled |
ORDER_EXPIRED | Expired |
| anything else | Unknown |
Signing
KBZ signs requests, the in-app orderInfo and notifications the same way: every non-empty field except sign and sign_type, sorted by key, joined as raw key=value pairs, with &key=<app key> appended, hashed with SHA-256 and uppercased. Numbers sign as the exact text sent and booleans as true / false; a notification with a nested object or array is rejected. The package signs every request and verifies every notification for you. For custom calls, the signer is public: $kbzPay->signer (a KbzPaySigner) has sign($fields) and verify($fields).
Errors
| Call | Throws | When |
|---|---|---|
new KbzPayPaymentData(...) | InvalidPaymentDataException | A value breaks the rules above. Nothing is sent |
pwa(), qr(), app() | ApiException | KBZ answers with an HTTP error, result other than SUCCESS or code other than 0, or without a prepay_id |
qr() | ApiException | KBZ returns no qrCode |
status() | ApiException | KBZ answers with an HTTP error, result other than SUCCESS or code other than 0, e.g. for an unknown order |
handleCallback() | SignatureVerificationException | sign doesn't match, or a field holds an object or array |
ApiException carries KBZ's code (e.g. ORDER_ID_USED, AOP08508) in gatewayCode and its msg in gatewayMessage. When KBZ can't be reached, the calls throw ApiException with httpStatus 0 and the original error as getPrevious().