Paywizard Integration
WizarPOS
  • Overview
  • Choose Your Best Practice
  • Cloud API
    • Quick Start - Cloud API
    • PayWizard Open Platform API Signature Guide V3
    • POS & Payment Terminal Binding Process
      • API 1: [Deprecated]Get Access Tokens
      • API 2: Bind POS & Payment Terminal
      • API 3: Get POS & Terminal Binding List
      • API : Unbind Terminal with POS
    • Do Transactions
      • API 4: POS Initiate Transaction
        • Transaction Request Example
      • API 5: POS System Query Transaction Results
      • Transaction Type
      • Terminal API: Subscribe Transaction Results
    • Get Transaction Result
      • API: Transaction Result Push
      • API: Get Transaction Result
      • API: Get Merchant Infomation
    • E-Receipt Intro
      • Terminal API : Upload Transaction Info
      • Terminal API : Upload Settlement Info
  • Semi integration
    • Quick Start - Semi Integration
    • Payment App Integration Protocol
    • Payment App AIDL Integration
  • payment parameter
    • Quick Start - Payment Parameter Push
    • TSYS Transit Parameter Push
    • Fiserv Parameter Push
    • Query Push Status
  • online card payment
    • Quick Start - Online Payment
    • Web Element Integration
    • Client Checkout Page SDK
  • APM (QR/WALLET)
    • Quick Start: QR Payment API Integration
    • Quick Pay - Merchant Scan
    • Generate QR Code - Customer Scan
    • Query Transaction Status
    • Refund
    • VOID
    • Close Order
  • loyalty
    • Quick Start - Loyalty API
    • Activate
    • Query
    • Top-up
    • Pay
    • Void
    • Issue Points
    • Redeem Points
    • Add Tip
Powered by GitBook
On this page
  1. APM (QR/WALLET)

Quick Pay - Merchant Scan

PreviousQuick Start: QR Payment API IntegrationNextGenerate QR Code - Customer Scan

Last updated 8 hours ago

CtrlK
  • Overview
  • Environments
  • Headers
  • Request Body Parameters
  • Request Example
  • Response Body
  • Success Response Example

Overview

This endpoint processes a payment using a customer-provided authorization code (often from a QR code or barcode on their device). This is typically used in a "merchant-scan" scenario where the merchant's point-of-sale system scans the customer's payment code.

Environments

Environment
Protocol
HTTP Method
URL

Sandbox

HTTPS

POST

https://uat.paywizard.biz/ovstrade/openPay/microPay

Production

HTTPS

POST

https://portal.paywizard.biz/ovstrade/openPay/microPay


Headers

Key
Type
Required
Description

Content-Type

String

Yes

Must be application/json.

jwt-token

String

Yes

The transaction token obtained using your developer credentials.

sign

String

Yes

Request Body Parameters

Parameter
Type
Required
Description

clientId

String

Yes

Your unique developer ID.

transIndexCode

String

Yes

The unique order ID generated by your system.

scanChannel

String

Yes

Request Example

{
    "clientId": "825429536610058240",
    "transIndexCode": "20250401123534801",
    "scanChannel": "M_PAY",
    "amount": "10.50",
    "authCode": "awrawfsfegojpenmfkapowngpawngpgrigawfnrtujgpsn",
    "tranCurrency": "USD"
}

Response Body

The response object contains the status of the request and the transaction details.

Parameter
Type
Description

code

Integer

The HTTP status code. 200 indicates a successful request. Any other value indicates an error.

msg

String

A human-readable message describing the result. "success" on successful requests.

timestamp

String

The UTC timestamp of the response. Format: YYYY-MM-DD HH:mm:ss.

data

Object

Success Response Example

Note: The parameter state in the example below corresponds to result in the documentation.

{
    "code": 200,
    "msg": "success",
    "timestamp": "2024-08-12 14:45:54",
    "data": {
        "mid": "10800000003",
        "paywizardId": "1000000011",
        "checkoutId": "768878984749514752",
        "transIndexCode": "202504011341223232135",
        "state": 0,
        "amount": "100.21"
    }
}

The request signature. See Signature Generation Guide.

The payment channel associated with the auth code. See Scan Channels for valid values.

amount

String

Yes

The total transaction amount. Example: "10.50".

authCode

String

Yes

The authorization code scanned from the customer's device.

tranCurrency

String

Yes

The 3-letter ISO currency code for the transaction. Example: "USD".

productDesc

String

No

A brief description of the product(s) or service(s).

payerType

String

Conditionally Required

The type of payer identifier. Valid values: MSISDN, EMAIL, PARTY_CODE. Required when scanChannel is MOMO.

notifyUrl

String

No

The callback URL where you will receive the final transaction result notification.

A container for the successful response data. Null on error.

data.mid

String

The merchant ID.

data.paywizardId

String

The unique platform ID for the transaction.

data.checkoutId

String

The unique transaction ID generated by the payment platform.

data.transIndexCode

String

The original third-party order ID from the request.

data.result

Integer

The status of the transaction. <br> 0: Success <br> 1: Failure <br> 2: Pending

data.amount

String

The transaction amount.