Paywizard DOCS
WizarPOS
  • Overview
  • Intro - Choose Your Best Practice
  • Cloud API
    • Quick Start - Cloud API
    • 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 Result Callback Interface
      • Transaction Type
      • Terminal API: Subscribe Transaction Results
  • HOST TO HOST INTEGRATION
    • Quick Start - Host to Host Integration
    • API: Transaction Result Push
    • API: Get Transaction Result
  • Semi integration
    • Payment App Integration Protocol
    • Payment App AIDL Integration
  • e-Receipt
    • e-Receipt Interface Intro
    • Terminal API : Upload Transaction Info
    • Terminal API : Upload Settlement Info
  • ONLINE PAYMENT INTEGRATION
    • Web Element Integration
    • Client Checkout Page SDK
Powered by GitBook
On this page
  • PayWizard Open Platform Payment Result Push Signature Verification
  • The general steps for signature generation are as follows:
  • Parameter signing example:
  • Transaction Result Push
  1. HOST TO HOST INTEGRATION

API: Transaction Result Push

PayWizard Open Platform Payment Result Push Signature Verification

The payload is signed using the developer key with SHA256.

The general steps for signature generation are as follows:

Step 1 : Set all sent or received data as set M, sort the parameters with non-empty values in set M by parameter name ASCII code from smallest to largest (dictionary order), and concatenate them into stringA using the URL key-value pair format (i.e., key1=value1key2=value2…).

Sort parameter names by ASCII code from smallest to largest (dictionary order).

Parameter names are case-sensitive.

Step 2: Append &clientId={clientId}&clientSecret={clientSecret} to the end of stringA to get the stringSignTemp string, then perform a SHA256 operation on stringSignTemp using the developer key to obtain the sign value signValue.

The values of clientId and clientSecret are the signature parameters provided by paywizard.

The sign field does not participate in the parameter sorting.

Parameter signing example:

invoiceNum=241224102701mid=10800000005respCode=000respDesc=APPROVALrrn=241224102706tradeNo=202412041080000000738tranTime=2024-12-24 07:27:16transId=000023transIndexCode=856602047078858752transResult=0transType=Purchase&clientId=83880518787948544&clientSecret=825997b5ab07e6a5bf71ff055d4a4a2

Transaction Result Push

Description

The third party provides the request address to push transaction results, requiring signature verification.

HTTP Header Information

Content-Type: application/json

Transaction Result Parameters

Name
Description
Mandatory
Type
Example
Description

checkoutId

Transaction Number

String

transIndexCode

External Third-Party System Order Number

String

paywizardId

PayWizard Number

String

mid

Acquiring Merchant Number

String

transType

Transaction Type

String

amount

Transaction Amount

String

state

Transaction Status

Integer

Transaction status 1: Pending Transaction 2: Transaction Completed 3: Revoked 4: Refund 5: Order Closed 6: Partial Refund 7: Pre-Authorization Completed 8: Pre-Authorization Revoked 9: Partial Revocation

currencyCode

Currency Code

String

840

tranTime

Transaction Time

LocalDateTime

yyyy-MM-dd HH:mm:ss

cardNo

Masked Card Number

String

cardToken

Card Token

String

transResult

Terminal Transaction Result

Integer

Terminal transaction result 0: Success 1: Failure 2: In Progress

transId

Terminal Acquiring Channel Transaction Serial Number

String

Returned when terminal transaction result is successful

invoiceNum

Terminal Transaction Invoice Number

String

Returned when terminal transaction result is successful

traceNum

Terminal Transaction Number

String

Returned when terminal transaction result is successful

rrn

Terminal Transaction Reference Number

String

Returned when terminal transaction result is successful

respCode

Terminal Transaction Response Code

String

Returned when terminal transaction is completed

respDesc

Terminal Transaction Response Description

String

Returned when terminal transaction is completed

notifyUrl

Message Push Address

String

sign

Signature String

String

PreviousQuick Start - Host to Host IntegrationNextAPI: Get Transaction Result

Last updated 1 month ago