AYA Pay

The AYA Payment Gateway is one hosted checkout for AYA Pay, other wallets (KBZ Pay, WavePay, UAB Pay, CB Pay…) and cards (VISA, Mastercard, JCB).

Call	What it does	Returns
aya.Services(ctx)	List the channels enabled for your account	[]ayapay.Service
aya.Initiate(data)	Signed form posted to AYA	*FormPayment
aya.Status(ctx, orderID)	Enquire an order	*PaymentStatusResult
aya.HandleCallback(request)	Verify the backend callback	*PaymentCallback
aya.VerifyRedirect(request)	Verify the customer's return	*PaymentCallback

Responses shows what AYA Pay puts in each result.

How it works

AYA posts the result to your callback URL and also signs the query string it adds when sending the customer back.

AYA Pay: channels, signed form, callback, return

Channels and Methods

Channel is a lowercase key such as aya_pay, kbz_pay or visa; Method is how the customer pays through it. Which ones you have depends on your merchant account, so list them:

import "github.com/laranex/go-myanmar-payments/v4/ayapay"

aya, err := ayapay.New(ayapay.Config{
	AppKey:         "...",
	AppSecret:      "...",
	TimeoutSeconds: 30,
}, nil)
if err != nil {
	return err
}

services, err := aya.Services(ctx)
if err != nil {
	return err
}
for _, service := range services {
	// service.Name: "AYA Pay"
	// service.Key: "aya_pay", pass it as Channel
	// service.ImageURL: the channel's logo
	// service.Methods: []ayapay.Method{ayapay.MethodQR, ayapay.MethodNoti}
	if service.Supports(ayapay.MethodQR) {
		// offer the QR method
	}
}

Methods AYA lists that this package doesn't know yet are kept in service.UnknownMethods.

ayapay.Method	Value	Customer
ayapay.MethodWeb	WEB	Pays on a hosted web page (cards)
ayapay.MethodQR	QR	Scans a QR with the wallet app
ayapay.MethodNoti	NOTI	Approves a push notification in the wallet app

Initiating a Payment

import (
	"fmt"
	"io"

	myanmarpayments "github.com/laranex/go-myanmar-payments/v4"
	"github.com/laranex/go-myanmar-payments/v4/ayapay"
)

data := ayapay.PaymentData{
	OrderID:     fmt.Sprintf("ORDER_%d", order.ID),
	Amount:      myanmarpayments.Kyat(10000),
	Channel:     "aya_pay",
	Method:      ayapay.MethodQR,
	ReturnURL:   "https://shop.test/payments/aya/return",
	Description: fmt.Sprintf("Order #%d", order.ID),
}

payment, err := aya.Initiate(data)
if err != nil {
	return err
}

// The page posts the signed form to AYA on load.
w.Header().Set("Content-Type", "text/html; charset=utf-8")
io.WriteString(w, payment.HTML())

ayapay.PaymentData

Field	Type	Required	Rules
OrderID	string	Yes	Unique, 6 to 40 characters (merchOrderId)
Amount	myanmarpayments.Amount	Yes	Whole kyat, greater than 0, e.g. Kyat(10000). AYA documents no decimals and only accepts MMK (104)
Channel	string	Yes	A key from Services
Method	ayapay.Method	Yes	MethodWeb, MethodQR or MethodNoti
ReturnURL	string	No	Absolute http or https URL. Empty uses the URL registered with AYA
Description	string	No	Shown to the customer
UserRefs	[]string	No	Up to 5 of your own values, echoed back in the callback

Form Encoding

AYA expects the form as multipart/form-data. payment.Enctype carries it; use it if you render the form yourself.

Handling Callbacks

AYA posts to the callback URL registered with them.

import (
	"net/http"

	myanmarpayments "github.com/laranex/go-myanmar-payments/v4"
)

// POST /payments/aya/callback
request, err := myanmarpayments.NewCallbackRequestFromHTTP(r)
if err != nil {
	http.Error(w, "invalid callback", http.StatusBadRequest)
	return
}
callback, err := aya.HandleCallback(request)
if err != nil {
	http.Error(w, "invalid callback", http.StatusBadRequest)
	return
}

if callback.IsSuccessful() {
	// callback.OrderID is your merchOrderId
	// callback.GatewayReference is AYA's tranId
}

callback.Acknowledgement.Write(w)

AYA signs only the fields present in its payload (wallet payments leave out the card fields); the package verifies them in the order the specification lists.

The Return Page

AYA signs the query string it adds when sending the customer back, so the return page can show the right message:

import (
	"io"
	"net/http"

	myanmarpayments "github.com/laranex/go-myanmar-payments/v4"
)

// GET /payments/aya/return
request, err := myanmarpayments.NewCallbackRequestFromHTTP(r)
if err != nil {
	http.Error(w, "invalid return", http.StatusBadRequest)
	return
}
result, err := aya.VerifyRedirect(request)
if err != nil {
	http.Error(w, "invalid return", http.StatusBadRequest)
	return
}

if result.IsSuccessful() {
	io.WriteString(w, "Thank you, your payment was received.")
	return
}
io.WriteString(w, "Payment "+string(result.Status)+".")

payload may be standard base64 with or without its = padding; partial padding, the URL-safe alphabet, line breaks and payloads that aren't UTF-8 JSON are rejected. A + in the base64 payload that reached you as a space (an unencoded query string) is read back as + before decoding; the checksum is still verified. Still fulfill orders from the backend callback.

Status Checks

import "fmt"

result, err := aya.Status(ctx, fmt.Sprintf("ORDER_%d", order.ID))
if err != nil {
	return err
}

if result.IsSuccessful() {
	// result.GatewayReference is AYA's tranId
}

Status takes your OrderID. An order AYA doesn't know returns *myanmarpayments.APIError (20 Transaction not found).

Responses

What AYA Pay puts in each field. See Results and PaymentCallback & Status for the full structs. On error the result is nil. A field the gateway didn't send is "". Raw holds plain Go values (JSON numbers become json.Numbers), while the typed fields such as Amount keep the exact text AYA sent.

Services() → []ayapay.Service

ayapay.Service is AYA-only, so it is listed in full here.

Field / Method	AYA Pay value
Name	AYA name, e.g. AYA Pay. Falls back to Key
Key	AYA key, e.g. aya_pay, kbz_pay, visa. Pass it as Channel. Always set
ImageURL	AYA image_url, the channel's logo. "" when AYA sends none
Methods	[]ayapay.Method this package knows, e.g. []ayapay.Method{ayapay.MethodQR, ayapay.MethodNoti}
UnknownMethods	[]string of methods AYA listed that this package doesn't know yet. Usually nil
Supports(method)	Whether Methods contains method

Entries AYA sends without a key are skipped.

Initiate() → *myanmarpayments.FormPayment

Field / Method	AYA Pay value
Flow()	FlowForm
OrderID	Your data.OrderID
Action	{BaseURL}/v1/payment/request, e.g. https://pgw.ayainnovation.com/v1/payment/request
Fields	The signed fields below, in signing order. Post them unchanged
Enctype	multipart/form-data
HTML()	A full HTML page that posts Fields to Action on load

Form field	Value
merchOrderId	data.OrderID
amount	data.Amount, e.g. 10000
appKey	Config.AppKey
timestamp	Unix time in seconds
userRef1 … userRef5	data.UserRefs, "" when unused
description	data.Description, "" when unset
currencyCode	104 (MMK)
channel	data.Channel, e.g. aya_pay
method	data.Method, e.g. QR
overrideFrontendRedirectUrl	data.ReturnURL, "" when unset
checkSum	HMAC-SHA256 of the values above joined with :

Initiate makes no HTTP call, so it takes no context. FormPayment has no Raw: nothing is sent to AYA until the customer's browser posts the form.

Status() → *myanmarpayments.PaymentStatusResult

Field	AYA Pay value
OrderID	AYA merchOrderId, falling back to the orderID you passed. Always set
Status	statusCode mapped, see Statuses
GatewayStatus	AYA statusCode, trimmed, e.g. 00
GatewayReference	AYA tranId
Amount	AYA amount, e.g. 10000
Raw	The verified, decoded enquiry payload: merchOrderId, tranId, amount, currencyCode, statusCode, paymentCardNumber, paymentMobileNumber, cardTypeName, cardExpiryDate, nameOnCard, approvalCode, tranRef, userRef1–5, description, dateTime

AYA leaves out the fields that don't apply (wallet payments have no card fields), so Raw only has the keys AYA sent. Some payloads spell currencyCode as currenyCode.

HandleCallback() → *myanmarpayments.PaymentCallback

Field	AYA Pay value
OrderID	AYA merchOrderId (your OrderID)
Status	statusCode mapped, see Statuses
GatewayStatus	AYA statusCode, trimmed, e.g. 00
GatewayReference	AYA tranId
Amount	AYA amount, e.g. 10000
Raw	The verified, decoded payload, with the same keys as Status()
Acknowledgement	HTTP 200, empty body, Content-Type: text/plain

VerifyRedirect() → *myanmarpayments.PaymentCallback

The same values as HandleCallback(), read from the signed payload and checkSum AYA adds to your return URL (query string first, then the body). There is nothing to acknowledge: render your own page.

Statuses

AYA statusCode	PaymentStatus
00	StatusSuccessful
01	StatusPending
02 (fail), 03 (reject)	StatusFailed
04	StatusExpired
anything else	StatusUnknown

Errors

Call	Returns	When
Initiate()	*InvalidPaymentDataError	data.Validate() fails. Nothing is signed
Services()	*APIError	AYA answers with an HTTP error or a status other than 00
Status()	*APIError	AYA answers with an HTTP error or a status other than 00, e.g. 20 Transaction not found
Status()	*SignatureVerificationError	The enquiry payload's checkSum doesn't match
HandleCallback(), VerifyRedirect()	*SignatureVerificationError	payload is missing or not base64 JSON, a signed field holds an object or array, or checkSum doesn't match

The error types live in the root myanmarpayments package. *APIError carries AYA's status (e.g. 20 Transaction not found, 09 Duplicate order ID) in GatewayCode and its message in GatewayMessage. When AYA can't be reached or ctx is canceled, the calls return *APIError, which unwraps to the cause (errors.Is(err, context.DeadlineExceeded)).