ChinaPay NetPayClient API Merchant Manual Net Pay Client

NetPayClient_Merchant_Manual

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 51

DownloadChinaPay NetPayClient API Merchant Manual Net Pay Client
Open PDF In BrowserView PDF
http://www.ChinaPay.com

ChinaPay
NetPayClient API Merchant Manual
(Version 2.5.23)

ChinaPay e-Payment Service Co.,Ltd
http://www.chinapay.com©Copyright 2014
ChinaPay e-Payment Service Co.,Ltd. All rights reserved.

http://www.ChinaPay.com

Revision History

Date

Version

2014-12-8

2.5.23

Description
1.Update the payment interface to
20141120, sign the whole packet

Author
Tang.yan

2. Modify the user manual of payment
interface in appendix B
2014-02-08

2.5.22

1. Add the description of orders uniqueness

Shane Zhang

2. Delete the chapter 3.3 KEYWORDS
3. Modify the file name and adjust format
2013-04-01

2.5.21

Add detailed description about Digital

Ye.qingqing

Envelope in chapter 3.4.5
2012-08-08

2.5.20

Change from transget to TransGet in

Xi.nan

chapter 7.5
2012-06-28

2.5.19

Add Appendix B about the Instructions for

Yu.shanshan/Ye.qingqi

Payment Interfaces

ng

Adjust the display format for Appendix
Add Question 2 and Question 4 in
Appendix A
Perfect the description about signature
function and verifying function in Qustion6
Appendix A
Add Error Code description about
-109,120,402 in Appendix C
2012-02-29

2.5.18

Add parameter BgRetUrl description in

Hu.jianlin

chapter 4.3
2010-2-18

2.5.17

Add function definition of PHP in Chapter

Zhou.yin/Ye.qingqing

3.5
2010-1-16

2.5.16

Change response code in the chapter of

Ye.qingqing

Query from ‖ResponseCode‖
to ‖ResponeseCode‖
2010-11-15

2.5.15

Change the value of return URLs in
Payment and Refund

Ye.qingqing

http://www.ChinaPay.com

2010-09-02

2.5.14

Modifying query version 20060831 digital

li.guolin

signature string field ` OrderId` to `OrdId`,
modifying java function reference link
`sign` to `Sign`
2010-08-24

2.5.13

NetPayClient_Merchant Operational
Manual domestic version.

li.guolin

http://www.ChinaPay.com

Contents
Backgrounds ................................................................................................................. 5
Introduction ................................................................................................................... 5
2.1. Object .................................................................................................................. 5
3. Summary ........................................................................................................................ 6
3.1. Why read this? .................................................................................................. 6
3.2. System environment ....................................................................................... 6
3.3. Basic concepts ................................................................................................. 6
3.3.1. Public-key Cryptography ......................................................................... 7
3.3.2. Secret-Key Cryptography ........................................................................ 7
3.3.3. Message-digest Algorithm ....................................................................... 8
3.3.4. Digital Signature........................................................................................ 8
3.3.5. Digital Envelope ...................................................................................... 10
3.4. Installing and deploying NetPayClient...................................................... 11
3.4.1. NetPayClient for Java Function Description ....................................... 11
3.4.2. NetPayClient for Win32 Function Description .................................... 15
3.4.3. NetPayClient for C Function Description ............................................ 20
3.4.4. NetpayClient for C# Function Description........................................... 26
3.4.5. NetpayClient for PHP Function Description ....................................... 31
4. Payment ........................................................................................................................ 35
4.1. Object ................................................................................................................ 35
4.2. Transaction process ...................................................................................... 35
4.3. Connection Approaches ............................................................................... 36
4.3.1. Connecting URL ..................................................................................... 36
4.3.2. Version ..................................................................................................... 36
5. Refund ........................................................................................................................... 38
5.1. Object ................................................................................................................ 38
5.2. Transaction Process...................................................................................... 39
5.3. Connecting Approaches ............................................................................... 39
5.3.1. Connection URL ..................................................................................... 39
5.3.2. Version ..................................................................................................... 39
6. Query ............................................................................................................................. 42
6.1. Object ................................................................................................................ 42
6.2. Transaction Process...................................................................................... 42
6.3. Connection Approaches ............................................................................... 43
6.3.1. Connection URL ..................................................................................... 43
6.3.2. Version ..................................................................................................... 43
Appendix A Common Connection Problems and Solutions .................................. 45
Appendix B The Instructions for Payment Interfaces .............................................. 48
Appendix C Response Code Description ................................................................. 49
1.
2.

4

http://www.ChinaPay.com

1. Backgrounds
ChinaPay commits herself to the development of e-payment service in China.
The thriving economic development of China has brought us not only the
e-commerce based on leading technology but also the concept of e-finance services.
Today, both traditional businesses and general consumers are in greater and higher need
for best-of-breed financial services. For businesses, the presence of e-commerce and
other brand-new business models impel them to request for high-grade electronization
and automatization of the financial services. While for consumers, their needs for personal
online financial services are continuously increasing as a result of life quality improvement.
ChinaPay, a new-born financial service representative, embraced the world leading
hi-technology into its professional financial services provided to businesses and
consumers in a customer-oriented manner. It is the aim to enable the whole society to
enjoy the e-payment service, to reduce costs, to enhance social working efficiency, and to
improve the living standard accordingly.
ChinaPay highly appreciates the great support from PBOC, local commercial banks
and SIIC in our process of development. We provide services including
enterprise-oriented e-payment resolutions and e-finance services focused on individual
consumers. Pursuing for breakthroughs and innovations, the products and resolutions
developed by ChinaPay integrate the Chinese-characterized professional financial
services with the modern hi-technology to meet the market demand and are also clinging
to the principle of professional, safe and easy to use. Employed by hundreds of
businesses and more than a hundred thousand consumers, ChinaPay’s e-payment
services have been proved to be a comprehensive and professional support for
businesses’ e-commerce as well as a secure and fast individual financial service for
general consumers.
ChinaPay is working to establish a nation-wide and multi-industry financial e-payment
network system. By cooperation with commercial banks and hi-tech enterprises, we will
be able to provide all-needs-met e-payment services to fulfill a common prosperity for all
parties involved.

2. Introduction
NetPayClient is an API Lib installed on the client side of ChinaPay’s authorized
merchants. It integrates with merchants’ online system to provide secure online payment
method between customers, merchants and banks. The main functions of this interface
below the list:

 The Pay online by bankcard.

 Refund the scuccessfully payment
 To inquire existing onlinepayment transactions
 To find the existing payment
2.1. Object
The main object of this manual is to help the member merchants of ChinaPay use the
5 / 51

http://www.ChinaPay.com

payment service interface- NetPayClient.
The document has four parts:
Summary: Introduces some basic concepts in the file, NetPayClient and its usage
Payment:Introduces required data field and content of payment interface
Refund: Introduces required data field and content of refund interface
Query: Introduces usage of transaction inquiry interface

3. Summary
3.1. Why read this?
The purpose of this document is to help ChinaPay’s merchants to understand
ChinaPay’s online transaction flows, NetPayClient installation and usage, which will
facilitate the system integration process with merchant’s online system.
This manual is intended as a guide for system developers, administration and
maintenance personnel of ChinaPay’s merchants. They are required to have basic
knowledge about the followings,
 Knowledge of operation systems, such as Microsoft Windows/NT、Windows9x、
Windows 2000、HP-UX、AIX、SUN Solaris、Linux、BSD.
 Knowledge of website configuration and web page development based on any of
the operation systems listed above.
 Development skills of standard CGI(Common Gateway Interface), ASP(Active
Server Pages), ISAPI, PHP or JAVA.
 Basic understandings of information security.
3.2. System environment
Merchants can choose the proper development and run-time environment according
to the practice. Currently, ChinaPay is able to support the following platforms and
development tools,
 NetPayClient for Java (in JAR,for Java development)
 NetPayClient for Win32 (in DLL,for Windows system development)
 NetPayClient for C (in.so or.a,for UNIX LINUX FreeBSD etc.development)
 NetPayClient for C# (in DLL,for Windows system development)

3.3. Basic concepts
With the development of computers and Internet, more and more businesses,
merchants and financial institutions have started to migrate their traditional business to the
Internet gradually so as to reduce costs, increase efficiency, explore new market areas
and improve service quality.
Internet is no longer a simple information exchange platform; instead it has grown up
into a global business network. Consequentially, network security is drawing more and
6 / 51

http://www.ChinaPay.com

more attention nowadays. What mean by network security is to solve the following
problems using all kinds of available technologies,
 Privacy – the information is protected from being sniffed by the third party during
transmission.
 Integration – the receiver is enabled to detect whether the information has been
changed during transmission or not.
 Authenticity – the receiver is able to identify the sender’s identity.
 Undeniability – the sender shall not be able to deny his sending activity as long
as the other party receives the effective information sent out.
Modern cryptography gives satisfying answers to these questions. As known,
encryption algorithms are responsible to solve the information privacy concern,
message-digest algorithms make it possible for integration checking, digital signature
enables the function of authentication and also avoids the deny after the event. Modern
cryptography comprises two systems; they are public-key cryptography and secret-key
cryptography. This chapter will explain some basic concepts briefly.
3.3.1. Public-key Cryptography
Public-key cryptography is also called asymmetrical cryptography, which utilizes two
keys, one for message encryption, and one for message decryption. This algorithm is
based on a mathematical relation between those two keys, so that the message encrypted
using either of the keys could only be decrypted using another key in the pair. Each user
owns a pair of keys, one is called private key that the user is responsible to keep it private,
and the other called public key is made widely available so that anyone can possess it.
Data encrypted with a public key can be decrypted only with the corresponding private key,
and vice versa. Currently, the most well known public key cryptography is called RSA
algorithm as it is invented by Rivest, Shamir and Adleman.

Figure 1 RSA Algorithm
3.3.2. Secret-Key Cryptography
Secret-key cryptography, known as symmetrical cryptography, employs only one key
for both encryption and decryption. A pair of users shares one secret key and is
responsible to keep it confidential between them. The message encrypted by the secret
key could only be decrypted using the same key. The most prevalent algorithms are
DES(Data Encryption Standard), 3DES etc.
7 / 51

http://www.ChinaPay.com

Figure 2. DES Algorithm
3.3.3. Message-digest Algorithm
Message-digest algorithm is a method taking a message of arbitrary length and
producing a message digest of fixed-length. The digests are sometimes called the ―digital
fingerprints‖ of data. A sound message-digest algorithm should have the following
features,
 It is almost impossible to find two such different byte streams that give the same
digest.
 If given a digest value, it is hard to invert, that is to say, it is computationally
infeasible to find the input message.
Before the sender sends a message, a message digest is applied to the message
and attached to it. Upon receiving, the recipient takes the original message and runs it
through the same message-digest algorithm to create his own local message digest value.
The recipient then compares the sender provided message digest with the locally
recovered message digest to check whether they are identical. If they are indeed identical,
this fact assures that there has been no change or tampering during transmission. The
widely used message-digest algorithm includes MD2 and MD5. Please check document
RFC1319 and RFC1321 for the usage of these two algorithms.

Figure 3. Message Digest
3.3.4. Digital Signature
A digital signature is an application that combines the asymmetrical cryptography with
message-digest algorithms. By using this, a digital signature authenticates the integrity of
8 / 51

http://www.ChinaPay.com

the signed data and the identity of the signatory. The following example explains the digital
signature process in details.

Figure 4 Digital Signature


Alice has a contract M.



Alice uses message-digest algorithm to calculate the message digest of the
contract M, say MD.



Alice uses asymmetric algorithm with her private key to sign the message digest
MD, and the result S is the so-called digital signature.



Alice attaches the contract M with the signature S, and then sends it to the
recipient, Bob, via the network.



Bob receives the contract M with the signature S sent by Alice.



Bob uses Alice’s public key to decrypt the signature S so as to obtain the
message digest MD which was prepared by Alice before sending.



Bob takes the originally unencrypted contract M and runs it through the same
message-digest algorithm to create his own local message digest MD’.



Bob compares MD and MD' to check if they are identical.



If they are indeed identical, then the message is verified. The recipient knows
that the signatory has sent the message because only the sender’s public key
9 / 51

http://www.ChinaPay.com

will work. The message was signed by no one other than himself, and that the
message has not been modified since he signed it.
3.3.5. Digital Envelope
A digital envelope is an application that combines the asymmetrical cryptography with
symmetrical cryptography. It is used to keep files transferring safety between two parties.
The following example explains the digital signature process in details.

Figure 5 Digital Envelope


Alice has a contract M.



Alice generates a random number.



Alice uses symmetrical cryptography with this random number as key file to
encrypt the contract M, and generate ciphertext contract.



Alice uses attaches asymmetrical cryptography with Bob’s public key to encrypt
the random number, and generate the envelope.



Alice sends the ciphertext contract and the envelope to Bob.



Bob receives the ciphertext contract and the envelope sent by Alice.



Bob uses his own private key to decrypt the envelope so as to obtain the
symmetric key (the random number).



Bob takes the symmetric key to decrypt the ciphertext contract and then get
contract M.
10 / 51

http://www.ChinaPay.com

3.4. Installing and deploying NetPayClient
3.4.1. NetPayClient for Java Function Description
NetPayClient is an API Lib installed on the client side of ChinaPay’s authorized
merchants. It integrates with the online system to provide secure online payment service
between customers, merchants and banks. Its main functions can be described as
follows:
. To generate digital signature for orders key information
. To verify the response of transaction results
. To generate digital signature for a digital string
. To verify digital signature of a digital string
3.4.1.1. File list
Name

Path

Usage

netpayclinet.jar

Installed in the corresponding path
according to the need of project

To provide the
method of deploying
digital signature

MerPrk.key

Unspecified, but needed to deploy
function appointed file path and file
name

Merchant’s private
key

PgPubk.key

Unspecified, but needed to deploy
function appointed file path and file
name

ChinaPay’s public
key

3.4.1.2. Functions Description
1) Function buildKey-to build public key/private key
 Function-Description:
public boolean buildKey (String MerId, int KeyUsage, String KeyFile)
 Function:
To build public key/private key for generating signature or verifying digital signature
 Parameter Description:
String MerId: merchant ID,it is defined as an array of digits with the length of 15
and is assigned by ChinaPay
int KeyUsage: the way of using public/private key, fixed value is 0
String KeyFile: file pathe of public/private key(including file name) e.g.
"d:\\MerPrk.key‖
 Return Value:
true: represents correct public/private key is found, and can use function of
digital signature and digital signature verification
false: represents failure of building public/private key, can’t use function of digital
signature and digital signature verification
 Note:
The method is in class chinapay. PrivateKey
11 / 51

http://www.ChinaPay.com

2) Function signOrder-to generate digital signature
 Function-Description:
public String signOrder(String MerId, String OrdId, String TransAmt, String CuryId,
String TransDate, String TransType)
 Function:
To generate digital signature for inputted parameters
 Parameter Description:





3)


String MerId – merchant ID, It is defined as a string with the length of 15 bytes
that is assigned by ChinaPay or the clearing bank when the merchant agrees to
use the service provided by ChinaPay.
String OrdId – order number. It is specified as a 16-byte long numeric string that
is generated by the merchant’s system, and previously failed transactions could
be paid again.
String TransAmt– transaction amount. This variable is defined as a numeric
string and has the length of 12. For example, the string ―000000001234‖
represents 12.34RMB in this case.
String CuryId – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
String TransDate– the date of the transaction. This numeric string is defined with
the length of 8 to represent the transaction date with the format of YYYYMMDD.
String TransType – the transaction type. It is a string sized 4 and values between
―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and ―0002‖
refers to refund transaction.
Return Value:
String CheckValue[256] --It is a digital signature string with the length of 256
bytes. It is generated using the input parameter values listed above.
Note:
The method is in class chinapay. SecureLink
Function verifyTransResponse-to verify transaction response
Function-Description:
public boolean verifyTransResponse(String MerId, String OrdId, String TransAmt,
String CuryId, String TransDate, String TransType, String OrderStatus, String
CheckValue)




Function:
To verify digital signature which inputs parameters
Parameter Description:
String MerId – merchant ID, It is defined as a string with the length of 15 bytes
that is assigned by ChinaPay or the clearing bank when the merchant agrees to
use the service provided by ChinaPay.
String OrdId – order number. It is specified as a 16-byte long numeric string that
is generated by the merchant’s system, and previously failed transactions could
be paid again.
String TransAmt– transaction amount. This variable is defined as a numeric
12 / 51

http://www.ChinaPay.com

string and has the length of 12. For example, the string ―000000001234‖
represents 12.34RMB in this case.
String CuryId – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
String TransDate– the date of the transaction. This numeric string is defined with
the length of 8 to represent the transaction date with the format of YYYYMMDD.
String TransType – the transaction type. It is a string sized 4 and values between
―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and
―0002‖ refers to refund transaction.
String OrderStatus– the status of the transaction. It is specified as an array of
numbers sized4. See the ―transaction response code table‖ for details.
String CheckValue - check value. It is the digital signature value with 256 bytes
generated by ChinaPay based on the transaction results.




4)




Return Value:
true : The value ―0‖ means that the method has been executed successfully. That
is to say, it is ChinaPay who sends the result to the merchant. And the merchant
will be responsible for the subsequent processing.
All the other return values indicate the failure of the function and the results can
be ignored or simply put into the ―garbage bin‖.
Note:
This method is in class chinapay. SecureLink
Function Sign-to generate digital signature for a string
Function-Description:
Public String Sign (String SignMsg)
Function:
To generate digital signature for inputted string of parameters
Parameter Description:
String SignMsg : is applied in the string for signature



5)


Return Value:
String CheckValue[256] -- It is a digital signature string with the length of 256
bytes. It is generated using the input parameter values listed above
Function verifyAuthToken- to verify signature for a string
Function-Description:
public boolean verifyAuthToken (String PlainData, StringCheckValue)



Function:
To verify the digital signature of target string



Parameter Description:
String PlainData- is applied in the string which generates digital signature
String CheckValue- Verification value, to verify signature of a 256-byte string
13 / 51

http://www.ChinaPay.com



Return Value:
True: represents success, otherwise is failure

3.4.1.3. Sample Codes
(the following code is not verified and only for reference)
 Sign Code
//initializing key files:
chinapay.PrivateKey key=new chinapay.PrivateKey();
chinapay.SecureLink t;
boolean flag;
String MerId, OrdId, TransAmt, CuryId, TransDate, TransType,ChkValue;
String plainData, ChkValue2 ;
flag=key.buildKey(MerId,0,"app/usr/chinapay/keys/MerPrk.key");
if (flag==false)
{
System.out.println("build key error!");
return;
}
t=new chinapay.SecureLink (key);
// sign to order
ChkValue= t.signOrder(MerId, OrdId, TransAmt, CuryId, TransDate, TransType) ;
// sign to a string
plainData = "test sign data ";
ChkValue2 = t.sign(plainData) ;



Verify Signature Sample Code

chinapay.PrivateKey key=new chinapay.PrivateKey();
chinapay.SecureLink t;
boolean flag;
boolean flag1;
String MerId, OrdId, TransAmt, CuryId, TransDate, TransType,ChkValue;
String plainData, ChkValue2
flag=key.buildKey("999999999999999",0,"c:\\winnt\\PgPubk.key");
if (flag==false)
{
msg="build key error!";
return;
}
t=new chinapay.SecureLink (key);
flag1=t.verifyTransResponse(MerId,OrdId, TransAmt, CuryId, TransDate, TransType, OrderStatus, ChkValue);
// ChkValue returned by ChinaPay response.
14 / 51

http://www.ChinaPay.com

if(flag1!=0) {
//handling the error of verifying signature.
}
// verifying the signature of a string
plainData = "test sign data ";
flag1 = t. verifyAuthToken (plainData, ChkValue2) ;

// ChkValue2 returned by ChinaPay response.

if(flag1) {
//handling the error of verifying signature.
}

3.4.2. NetPayClient for Win32 Function Description
3.4.2.1. File list
Name

Path

Usage

netpay.dll

The same path as ChinaPay.dll ,
or copy the file to
c:\winnt\system32(c:\windows\syst
em for win95,98,etc)

To provide the function
of order sign and
ChinaPay’s signature
verification

netpay.lib

Unspecified (such as c:\netpay)

This file is required
when invoking
netpay.dll for compiling

MerPrk.key

Copy to the same path as windows
c:\winnt for NT OR c:\windows for
win95,98; or Unspecified, but
needed to deploy function
appointed file location and file
name

Merchant’s private key

PgPubk.key

Copy to the same path as windows
c:\winnt for NT OR c:\windows for
win95,98; or Unspecified, but
needed to deploy function
appointed file path and file name

ChinaPay’s public key

ChinaPay.dll

Unspecified (such as c:\netpay)

Method package with
netpay.dll in COM,
need to register with
regsvr32

Installation procedure
 Install automatically
Unzip the netpay package for NT platform and run NetPay4NTSetup.exe. The
program will copy the files to the specified directory.
 Install manually
15 / 51

http://www.ChinaPay.com

If there is exception thrown out during installation (probably due to the system
abnormity), you may need to follow the procedures below to install the software manually.

Copy all the key files to the specified directory.

Register ChinaPay.dll by entering ―regsvr32 [the path of gensign]‖ in the
command line. This control can only work in a VC environment, it is suggested to
use ―Dependency Walker‖ to make sure that this DLL file has been set correctly.
3.4.2.2. Functions Description:
1) Set Private Key Path- setMerKeyFile
 Function Descripiton
void setMerKeyFile (String KeyFile)


Function
Set private key path

 Parameters Descripiton:
String KeyFile: file path of private key(including file name) e.g. "d:\\MerPrk.key
2)


Unset private key path-unsetMerKeyFile
Function Descripiton
void unsetMerKeyFile ()

 Function
Unset previous private key path, recover default private key path


Parameters Descripiton:
None

3)


Set ChinaPay Public Key Path-setPubKeyFile
Function Descripiton
void setPubKeyFile (String KeyFile)



Function
Set ChinaPay Public Key path

 Parameters Descripiton:
String KeyFile: file path of private key(including file name) e.g.:"d:\\ PgPubk.key‖
4)


Unset public key path- unsetPubKeyFile
Function Descripiton
void unsetPubKeyFile ()



Function
Unset previous ChinaPay public key path which setPubKeyFile sets, recover
default public key path
16 / 51

http://www.ChinaPay.com



Parameters Descripiton:
None

5)


Function sign-generate digital signature for order
Function Descripiton
public String sign (String MerId, String OrdId, String TransAmt, String CuryId,
String TransDate, String TransType)



Parameters Descripiton:











String MerId – merchant ID, It is defined as a string with the length of 15
bytes that is assigned by ChinaPay or the clearing bank when the merchant
agrees to use the service provided by ChinaPay.
String OrdId – order number. It is specified as a 16-byte long numeric string
that is generated by the merchant’s system, and previously failed
transactions could be paid again.
String TransAmt– transaction amount. This variable is defined as a numeric
string and has the length of 12. For example, the string ―000000001234‖
represents 12.34RMB in this case.
String CuryId – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
String TransDate– the date of the transaction. This numeric string is defined
with the length of 8 to represent the transaction date with the format of
YYYYMMDD.
String TransType – the transaction type. It is a string sized 4 and values
between ―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment
transaction and ―0002‖ refers to refund transaction.

 Return values:
String CheckValue[256] -- It is a digital signature string with the length of 256 bytes. It
is generated using the input parameter values listed above
 Note:
If COM is not called, load netpay.dll with LoadLibrary, need to find corresponding
name with Dependency Walker.
6)


Function check-to verify transaction response
Function Descripiton
public String check(String MerId, String OrdId, String TransAmt, String CuryId,
String TransDate, String TransType, String OrderStatus, String CheckValue)



Parameters Descripiton:
String MerId – merchant ID, It is defined as a string with the length of 15 bytes
that is assigned by ChinaPay or the clearing bank when the merchant agrees to
use the service provided by ChinaPay.
17 / 51

http://www.ChinaPay.com



String OrdId – order number. It is specified as a 16-byte long numeric string that
is generated by the merchant’s system, and previously failed transactions could
be paid again.
String TransAmt– transaction amount. This variable is defined as a numeric
string and has the length of 12. For example, the string ―000000001234‖
represents 12.34RMB in this case.
String CuryId – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
String TransDate– the date of the transaction. This numeric string is defined with
the length of 8 to represent the transaction date with the format of YYYYMMDD.
String TransType – the transaction type. It is a string sized 4 and values between
―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and ―0002‖
refers to refund transaction.
String OrderStatus– the status of the transaction. It is specified as an array of
numbers sized 4. See the ― transaction response code table‖ for details.
String CheckValue – check value. It is the digital signature value with 256 bytes
generated by ChinaPay based on the transaction results.
Return values:
true : The value ―0‖ means that the method has been executed successfully. That

is to say, it is ChinaPay who sends the result to the merchant. And the merchant
will be responsible for the subsequent processing.
All the other return values indicate the failure of the function and the results can
be ignored or simply put into the ―garbage bin‖.


Note:
If COM is called, method return value is ―0‖ in string—means signature
verification successful.

7) Function signData-to generate digital signature for a string
 Function Descripiton
Public String Sign (String MerId, String SignMsg)



Parameters Descripiton:
String MerId:
merchant ID, It is defined as a string with the length of 15 bytes
that is assigned by ChinaPay.
String SignMsg : is applied in the string for signature.





Return values:
String CheckValue[256] -- It is a digital signature string with the length of 256
bytes. It is generated using the input parameter values listed above
Note:
If COM is not called, load netpay.dll with LoadLibrary, need to find
corresponding name with Dependency Walker
18 / 51

http://www.ChinaPay.com

8)


Function checkData- to verify signature for a string
Function Descripiton
public String checkData (String PlainData, String CheckValue)



Parameters Descripiton:
String PlainData- is applied in the string which generates digital signature
String CheckValue- Verification value, to verify signature of a 256-byte string



Return values:
―0‖: represents success, otherwise is failure



Note:
If COM is called, method return value is ―0‖ in string—means signature
verification successful.

3.4.2.3. Sample Codes
Take C# for example:
First, transform Com type information into .NET digits tlbimp ChinaPay.dll /out:
ChinaPay_tsl.dll (tlbimp is the tool vs.net provides) in the project, if project->add
reference,select com,input ChinaPay_tsl.dll
(the following code is not verified and only for reference)
 Sign Sample Codes
using System;
using ChinaPay_tsl;

namespace ConsoleApplication1
{
class Class1
{
[STAThread]
public static void Main()
{
//Sign
NetPayClientClass a = new NetPayClientClass();
//Set private key path
a.setMerKeyFile("D:\\ MerPrK.key");

// if this method is not called, it will proceed
according to the default path

String ChkValue;
String MerId;

//merchant id

//Sign order
19 / 51

http://www.ChinaPay.com

ChkValue=a.sign(MerId,"0000000000000001","000000001234","156","20070123",
"0001");
// Sign a string
String ChkValue2;
String plainData =

"test sign data ";

ChkValue2= a.signData(MerId,plainData);
}
}
}



Verify Signature Sample Codes
using System;
using ChinaPay_tsl;

namespace ConsoleApplication1
{
class Class1
{
[STAThread]
public static void Main()
{
//verify signature
NetPayClientClass a = new NetPayClientClass();
//set private key path
a.setPubKeyFile("D:\\ PgPubk.key");

// if this method is not called, it will proceed
according to the default path

]

String ChkValue;

String MerId; //merchant id
//sign order
string flag =
a.check(MerId,"070699060500011","000000010000","156","20070615","0001","1001",
ChkValue); // ChkValue is return value which ChinaPay sends to merchant

// sign a string
String ChkValue2;
String plainData =

"test sign data ";

ChkValue2= a.signData(MerId,plainData);
}
}
}

3.4.3. NetPayClient for C Function Description
3.4.3.1. File List
File name

File path

Usage
20 / 51

http://www.ChinaPay.com

netpayclient.h

Unspecified

Applied in import file of C
language etc

libnpc.so / libnpc.a

Unspecified

Method lib of signature dat
a
and signature verification
(
apply for .so or .a accordi
ng to merchants’ conditi
on)

MerPrk.key

Set NPCDIR environment variabl
e appointed file path, can’t cha
nge file name or appoint NPCDI
R environment variable, but nee
d to call method appointed file
path and name

Merchant signature private
key

PgPubk.key

Set NPCDIR environment variabl
e appointed file path, can’t cha
nge file name or appoint NPCDI
R environment variable, but nee
d to call method appointed file
path and name

ChinaPay signature public
key

3.4.3.2. Functions Description
1)


Set Private Key Path- setMerKeyFile
Function Descripiton
void setMerKeyFile (char keyFile[256])



Function
Set private key path.



Parameters Descripiton:
char KeyFile: file path of private key(including file name) e.g. "d:\\MerPrk.key‖
2)


Unset private key path-unsetMerKeyFile
Function Descripiton
Function Description: void unsetMerKeyFile ()

 Function
Unset previous private key path, recover default private key path
 Parameters Descripiton:
None
3)

Set ChinaPay Public Key Path-setPubKeyFile
21 / 51

http://www.ChinaPay.com



Function Descripiton
void setPubKeyFile (char keyFile[256])



Function
Set ChinaPay Public Key path



Parameters Descripiton:
char keyFile: file path of private key(including file name) e.g.:"d:\\ PgPubk.key‖

4)


Unset public key path- unsetPubKeyFile
Function Descripiton
void unsetPubKeyFile ()



Function
Unset previous ChinaPay public key path which setPubKeyFile sets, recover
default public key path

 Parameters Descripiton:
None
5)


Generate digital signature Function – signOrder
Function Descripiton
int signOrder(char MerId[15], char OrdId[16], char TransAmt[12], char CuryId[3],
char TransDate[8], char TransType[4], char CheckValue[256])



Function
To generate digital signature for inputted parameters



Parameters Descripiton:
char MerId[15] – merchant ID. It is defined as an array of digits with the length of
15. ChinaPay or the clearing bank assigns it to the authorized merchants.
char OrdId[16] – order number. It is an array of numbers and has the length of 16,
generated by the merchant’s system and only the previously failed orders are
allowed to be performed again.
char TransAmt[12] – transaction amount. It is specified as an array of numbers
sized 12. For example, the value of ―000000001234‖ represents 12.34RMB in
this case.
char CuryId[3] – the type of the currency used. It is an array of numbers and has
a size of 3. Currently, only the value of ―156‖ is accepted to express RMB.
char TransDate[8] – the date of the transaction. This variable is defined as an
array of numbers sized 8 and the format defined is YYYYMMDD.
char TransType[4] – the type of the transaction. It is a four-bytes long array and
values between ―0001‖ and ―0002‖. ―0001‖ represents payment transaction and
―0002‖ refers to refund transaction.
22 / 51

http://www.ChinaPay.com



char OrderStatus[4] – the status of the transaction. It is specified as an array of
numbers sized 4. See the ― transaction response code table‖ for details.
char CheckValue[256] – check value. It is the digital signature value generated
by ChinaPay based on the transaction results.
Return values:
The value ―0‖ means that the method has been executed successfully. Otherwise
means failure.

6)


Verify transaction response –verifyTransResponse
Function Descripiton
int verifyTransResponse(char MerId[15], char OrdId[16], char TransAmt[12],
char CuryId[3], char TransDate[8], char TransType[4], char OrderStatus[4], char
CheckValue[256])



Function
To verify digital signature which inputs parameters



Parameters Descripiton:
String MerId[15] – merchant ID, It is defined as a string with the length of 15
bytes that is assigned by ChinaPay or the clearing bank when the merchant
agrees to use the service provided by ChinaPay.
String OrdId[16] – order number. It is specified as a 16-byte long numeric string
that is generated by the merchant’s system, and previously failed transactions
could be paid again.
String TransAmt[12] – transaction amount. This variable is defined as a numeric
string and has the length of 12. For example, the string ―000000001234‖
represents 12.34RMB in this case.
String CuryId[3] – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
String TransDate[8] – the date of the transaction. This numeric string is defined
with the length of 8 to represent the transaction date with the format of
YYYYMMDD.
String TransType[4] – the transaction type. It is a string sized 4 and values
between ―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction
and ―0002‖ refers to refund transaction.
String OrderStatus[4] – the status of the transaction. It is specified as an array of
numbers sized4. See the ― transaction response code table‖ for details.
String CheckValue[256] - check value. It is the digital signature value with 256
bytes generated by ChinaPay based on the transaction results.



Return values:
The value ―0‖ means that the method has been executed successfully. That is to
say, it is ChinaPay who sends the result to the merchant. And the merchant will be
responsible for the subsequent processing. All the other return values indicate the
failure of the function and the results can be ignored or simply put into the ―garbage
23 / 51

http://www.ChinaPay.com

bin‖.
 Note:
7) generate digital signature for a string – signData
 Function Descripiton
int signData (char MerId[15],char *SignMsg,char ChkValue[256])


Function
To generate digital signature for inputted string of parameters



Parameters Descripiton:
char MerId[15] - merchant ID, It is defined as a string with the length of 15 bytes
that is assigned by ChinaPay
char *SignMsg - is applied in the string for signature
char CheckValue[256] -It is a digital signature string with the length of 256 bytes.
It is generated using the input parameter values listed above



Return values:
0 means successful, otherwise is error codes.

8)


Verify signature for a string –verifySignData
Function Descripiton
int verifySignData (char * PlainData, char CheckValue[256])



Function
To verify the digital signature of target string



Parameters Descripiton:
char* PlainData - is applied in the string which generates digital signature
char CheckValue[256]- Verification value, to verify signature of a 256-byte
string



Return values:
The value ―0‖ means that the method has been executed successfully. That is to
say, it is ChinaPay who sends the result to the merchant. And the merchant will
be responsible for the subsequent processing. All the other return values indicate
the failure of the function and the results can be ignored.

3.4.3.3. Sample Codes
 Sign Sample Codes
(the following code is not verified and only for reference)
#include 
#include 
24 / 51

http://www.ChinaPay.com

#include "netpayclient.h"

int main (int argc, char* argv[])
{
char MerId[16];
char OrdId[17];
char TransAmt[13];
char CuryId[4];
char TransDate[9];
char TransType[5];
char ChkValue[257];
int flag;

setMerKeyFile("/app/netpay/key/MerPrk.key");

// if it is not set, files will be acquired

according to NPCDIR environment variables

// Sign an order
flag =signOrder(MerId, OrdId, TransAmt, CuryId, TransDate, TransType, ChkValue);
if(flag != 0) {
//signature failure
}

// sign a string
plainData = "test sign data ";
flag = signData (MerId ,plainData, ChkValue);

// ChkValue is the signature of the string

if(flag != 0) {
//signature failure
}
}



Verify Signature Sample Code
(the following code is not verified and only for reference)
#include 
#include 
#include "netpayclient.h"

int main (int argc, char* argv[])
{
char MerId[16];
char OrdId[17];
char TransAmt[13];
char CuryId[4];
char TransDate[9];
25 / 51

http://www.ChinaPay.com

char TransType[5];
char ChkValue[257];
char OrderStatus[5];
int flag;

setPubKeyFile ("/app/netpay/key/PubPrk.key"); // if it is not set, files will be acquired
according to NPCDIR environment variables

// receive fields that ChinaPay returns: MerId, OrdId, TransAmt, CuryId, TransDate,
TransType OrderStatus ,ChkValue

// sign the verified order

flag = verifyTransResponse(MerId, OrdId, TransAmt, CuryId, TransDate, TransType,
OrderStatus ,ChkValue);
if(flag != 0) {
//signature failure
}

// sign a string
plainData = "test sign data ";
flag = verifySignData (plainData, ChkValue);

// ChkValue is the signature that ChinaPay

returns
if(flag != 0) {
//signature failure
}
}

3.4.4. NetpayClient for C# Function Description
3.4.4.1. File List
File name

File path

Usage

netpay.dll

Installed in the corresponding path
according to the need of project

To provide the method of dep
loying digital signature.

MerPrk.key

Unspecified saving path, but the fu
nction need to specify file path and
file name.

Merchant’s private key for sig
nature.

PgPubk.key

Unspecified saving path, but the fu
nction need to specify file path and
file name.

ChinaPay public key for signa
ture.




Saving the netpay.dll at specify path according to the need of project.
In developing environment, by using‖Adding Adduction‖ adds the netpay.dll into
project, and could be called directly.

3.4.4.2. Functions Description
26 / 51

http://www.ChinaPay.com

1)


Build public key/private key object buildKey
Function Descripiton
public boolean builtKey (String MerId, int KeyUsage, String KeyFile)



Function
Used to build public key/private key object for generating signature or verifying
digital signature.



Parameters Descripiton:
String MerId merchant ID,it is defined as an array of digits with the length of 15
and is assigned by ChinaPay.
int KeyUsage the way of using public/private key, fixed value is 0.
String KeyFile file pathe of public/private key(including file name) e.g.
"d:\\MerPrk.key‖



Return values:
true: represents correct public/private key is found, and can use function of
digital signature and digital signature verification
false: represents failure of building public/private key, can’t use function of digital
signature and digital signature verification



Note:
In netpay. NETPAY, this function can judge the status of current public key/private key by
NetPay.NETPAY.PrivateKeyFlag or NetPay.NETPAY.PublicKeyFlag

2)


Function signOrder – to generate digital signature
Function Descripiton
public String signOrder(String MerId, String OrdId, String TransAmt, String CuryId,
String TransDate, String TransType)



Function
To generate digital signature for inputted parameters.



Parameters Descripiton:
String MerId – merchant ID, It is defined as a string with the length of 15 bytes
which is assigned by ChinaPay or the clearing bank when the merchant agrees
to use the service provided by ChinaPay.
String OrdId – order number. It is specified as a 16-byte long numeric string that
is generated by the merchant’s system, and previously failed transactions could
be paid again.
String TransAmt– transaction amount. This variable is defined as a numeric
string and has the length of 12. For example, the string ―000000001234‖
represents 12.34RMB in this case.
String CuryId – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
27 / 51

http://www.ChinaPay.com

String TransDate– the date of the transaction. This numeric string is defined with
the length of 8 to represent the transaction date with the format of YYYYMMDD.
String TransType – the transaction type. It is a string sized 4 and values between
―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and ―0002‖
refers to refund transaction.




Return values:
String CheckValue[256] -- It is a digital signature string with the length of 256
bytes. It is generated using the input parameter values listed above
Note:
The method is in class netpay. NETPAY

3)


Function verifyTransResponse-to verify transaction response
Function Descripiton
public boolean verifyTransResponse(String MerId, String OrdId, String TransAmt,
String CuryId, String TransDate, String TransType, String OrderStatus, String
CheckValue)



Function
To verify digital signature which inputs parameters



Parameters Descripiton:
String MerId – merchant ID, It is defined as a string with the length of 15 bytes
that is assigned by ChinaPay or the clearing bank when the merchant agrees to
use the service provided by ChinaPay.
String OrdId – order number. It is specified as a 16-byte long numeric string that
is generated by the merchant’s system, and previously failed transactions could
be paid again.
String TransAmt– transaction amount. This variable is defined as a numeric
string and has the length of 12. For example, the string ―000000001234‖
represents 12.34RMB in this case.
String CuryId – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
String TransDate– the date of the transaction. This numeric string is defined with
the length of 8 to represent the transaction date with the format of YYYYMMDD.
String TransType – the transaction type. It is a string sized 4 and values between
―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and
―0002‖ refers to refund transaction.
String OrderStatus– the status of the transaction. It is specified as an array of
numbers sized4. See the ― transaction response code table‖ for details.
String CheckValue - check value. It is the digital signature value with 256 bytes
generated by ChinaPay based on the transaction results.



Return values:
true : means that the method has been executed successfully. That is to say, it is
28 / 51

http://www.ChinaPay.com

ChinaPay who sends the result to the merchant. And the merchant will be
responsible for the subsequent processing. All the other return values indicate
the failure of the function and the results can be ignored or simply put into the
―garbage bin‖.


Note:
This method is in class netpay. NETPAY

4)


Function Sign-to generate digital signature for a string
Function Descripiton
Public String Sign (String SignMsg)



Function
To generate digital signature for inputted string of parameters



Parameters Descripiton:
String SignMsg : is applied in the string for signature



Return values:
String CheckValue[256] -- It is a digital signature string with the length of 256
bytes. It is generated using the input parameter values listed above

5)


Function verifyAuthToken- to verify signature for a string
Function Descripiton
public boolean verifyAuthToken (String PlainData, StringCheckValue)



Function
To verify the digital signature of target string



Parameters Descripiton:
String PlainData- is applied in the string which generates digital signature
String CheckValue- Verification value, to verify signature of a 256-byte string



Return values:
True: represents success, otherwise is failure

 Note:
This method is in class netpay. NETPAY
3.4.4.3. Sample Codes
(the following code is not verified and only for reference)
29 / 51

http://www.ChinaPay.com



Sign Code

string MerId, OrdId, TransAmt, CuryId, TransDate, TransType,ChkValue;
string plainData, ChkValue2 ;

//initialize key file
if (NetPay.NETPAY.buildKey("808080290000001", 0, "c:\\key\\MerPrk.key"))
{
showInfo(">> set private key: succeed.\r\n\r\n");
}

// signature for the order
if (NetPay.NETPAY.PrivateKeyFlag)
{
string ChkValue = NetPay.NETPAY. signOrder(MerId, OrdId, TransAmt, CuryId, TransDate,
TransType) ;
showInfo(">>ostr: " + ostr + "\r\n\r\n");
showInfo(">>ChkValue :" + ChkValue + "\r\n\r\n");
}

// signature for a string
string plainData = "8080802900000010000000010273765000000000001156201008060001";
if (NetPay.NETPAY.PrivateKeyFlag)
{
string ChkValue2 = NetPay.NETPAY. Sign(plainData);
showInfo(">>ostr :" + ostr + "\r\n\r\n");
showInfo(">>ChkValue: " + ChkValue + "\r\n\r\n");
}



Verify Signature Sample Code

String MerId, OrdId, TransAmt, CuryId, TransDate, TransType,ChkValue;
String plainData, ChkValue2
//initializing key file
if (NetPay.NETPAY.buildKey("999999999999999", 0, "c:\\key\\PgPubk.key"))
{
showInfo(">>set public key:succeed.\r\n\r\n");
}

//verify signature of order
if (NetPay.NETPAY.PublicKeyFlag)
{
bool flag= NetPay.NETPAY.verifyTransResponse(MerId,OrdId, TransAmt, CuryId, TransDate,
TransType, OrderStatus, ChkValue); // ChkValue is returned by ChinaPay response.
showInfo(">>ostr:" + ostr + "\r\n\r\n");
30 / 51

http://www.ChinaPay.com

showInfo(">>check:" + check + "\r\n\r\n");
showInfo(">> verify signature:" + result + "\r\n\r\n");
if(!flag) {
// error of signature verification
}
}

// verifying the signature of a string
plainData = "test sign data ";

if (NetPay.NETPAY.PublicKeyFlag)
{
bool result = NetPay.NETPAY.verifyAuthToken(plainData, ChkValue2); // ChkValue2 returned
by ChinaPay response
showInfo(">>ostr:" + ostr + "\r\n\r\n");
showInfo(">>check:" + check + "\r\n\r\n");
showInfo(">>verifying signature: " + result + "\r\n\r\n");
if(!flag) {
// error of signature verification
}
}

3.4.5. NetpayClient for PHP Function Description
3.4.5.1. File List
Name

Path

Usage

netpayclinet.php

Installed in the corresponding path
according to the need of user

To provide the
method of deploying
digital signature

MerPrk.key

Unspecified, but needed to deploy
function appointed file path and file
name

Merchant’s private
key

PgPubk.key

Unspecified, but needed to deploy
function appointed file path and file
name

ChinaPay’s public
key

3.4.5.2. Functions Description
1) Function buildKey-to build public key/private key
 Function-Description:
function buildKey ($keyfile)
 Function:
To build public key/private key for generating signature or verifying digital signature
 Parameter Description:
$keyfile: file path of public/private key(including file name) e.g.
"d:\\MerPrk.key‖,support relative path
31 / 51

http://www.ChinaPay.com



Return Value:
true: return 15 bytes merchant id, else is false

2)


Function signOrder-to generate digital signature
Function-Description:
function signOrder($merid, $ordno, $amount, $curyid, $transdate, $transtype)
Function:
To generate digital signature for inputted parameters
Parameter Description:






3)


$merid
– merchant ID, It is defined as a string with the length of 15 bytes
that is assigned by ChinaPay.
$ordno
– order number. It is specified as a 16-byte long numeric string that
is generated by the merchant’s system, and previously failed transactions could
be paid again.
$amount – transaction amount. This variable is defined as a numeric string and
has the length of 12. For example, the string ―000000001234‖ represents
12.34RMB in this case.
$curyid – the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
$transdate – the date of the transaction. This numeric string is defined with the
length of 8 to represent the transaction date with the format of YYYYMMDD.
$transtype –the transaction type. It is a string sized 4 and values between
―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and ―0002‖
refers to refund transaction.
Return Value:
NetPayClient generates a digital signature string with the length of 256 bytes
using the input parameter values listed above. If the length of input parameter is
invalid, the function return false.
Function verifyTransResponse-to verify transaction response
Function-Description:
function verifyTransResponse($merid, $ordid, $amount $curyid, $transdate,
$transtype, $status, $checkvaluue)




Function:
To verify digital signature is right or not
Parameter Description:
$merid – merchant ID, It is defined as a string with the length of 15 bytes that
is assigned by ChinaPay.
$ordid – order number. It is specified as a 16-byte long numeric string that is
generated by the merchant’s system, and previously failed transactions could be
paid again.
$amount – transaction amount. This variable is defined as a numeric string
and has the length of 12. For example, the string ―000000001234‖ represents
12.34RMB in this case.
32 / 51

http://www.ChinaPay.com

$curyid
– the type of the currency used. It is a string containing 3 bytes.
Currently, only the value ―156‖ is accepted to represent RMB in the system.
$transdate – the date of the transaction. This numeric string is defined with the
length of 8 to represent the transaction date with the format of YYYYMMDD.
$transtype – the transaction type. It is a string sized 4 and values between
―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and
―0002‖ refers to refund transaction.
$status– the status of the transaction. It is specified as an array of numbers
sized4. See the ―transaction response code table‖ for details.
$checkvalue - check value. It is the digital signature value with 256 bytes
generated by ChinaPay based on the transaction results.


Return Value:
true means that the method has been executed successfully. That is to say,
it is ChinaPay who sends the result to the merchant. And the merchant will be
responsible for the subsequent processing.
All the other return values indicate the failure of the function and the results
can be ignored or simply put into the ―garbage bin‖.

4)


Function sign-to generate digital signature for a string
Function-Description:
function sign ($msg)
Function:
To generate digital signature for inputted string of parameters
Parameter Description:




$msg

: is applied in the string for signature



Return Value:
NetPayClient generates a digital signature string with the length of 256 bytes
using the input parameter values listed above.
5)


Function verify- to verify signature for a string
Function-Description:
function verify ($plain, $checkvalue)



Function:
To verify the digital signature of target string



Parameter Description:
$plain - is applied in the string which generates digital signature
$checkvalue - Verification value, to verify signature of a 256-byte string
 Return Value:
True: represents success, otherwise is failure
3.4.5.3. Sample Codes
33 / 51

http://www.ChinaPay.com

(the following code is not verified and only for reference)
 Sign Code




Verify Signature Sample Code

验证签名失败!";
exit;
}
?>

4. Payment
4.1. Object
This chapter mainly instructs ChinaPay’s merchants to connect with payment platform.
In this way, merchants can develop their online payment transactions.
4.2. Transaction process
Card holders generate the order information from the merchant website, through the
public payment gateway subsystem platform to do the payment process. The transaction
processing includes order confirmation, payment processing, and payment complete
three parts. More details as following:
【Step one】order confirmation
1. The card holder browse the website of merchant, chooses the payment options,
generate the order information.
2. The card holder confirms order information, start payment process.
【Step two】payment processing
3. the card holder confirms the payment information, and the merchant website begin
to applying the gateway for payment, then the gateway verify the validity of merchant
and the integrality of message.
4. The payment gateway show the interface of payment channels, and card holder
chose the payment channel.
5. Card holder input accounts and password and other verified information for safety
on the channel he/she selected.
6. After the confirmation of card holder’s safe information, begin the payment.
35 / 51

http://www.ChinaPay.com

【Step three】payment complete
7. Payment channel return the payment result to the payment gateway.
8. Payment gateway shows the payment result to card holder, meanwhile informs
merchant the payment result of website.
9. Website shows card holder the result of merchant.
10. The payment complete.
4.3. Connection Approaches
4.3.1. Connecting URL
Merchant can connect with ChinaPay’s online payment system by the means of WEB
service. URL of receiving transaction data is:
Test Environment:http://payment-test.chinapay.com/pay/TransGet
Production Environment:https://payment.chinapay.com/pay/TransGet
4.3.2. Version
payment version: 20141120


Content Submitted on Transaction Page

Merchant submits order information to ChinaPay’s payment connection URL.
Content of the FORM on transaction page should include(do remember to distinguish
capital letters and small letters):
(the content of action is the URL address to submit transaction data) ((MerId is the Merchant ID assi gned by ChinaPay, length of 15 bytes, necessary) (Order ID merchants submits to ChinaPay, length of 16 bytes, necessary) (Order transaction amount, wit h 2 decimal,length of 12 bytes, add 0 from the left if inadequate, necessary) (Order transaction currency, length of 3 byt es, only for Renminbi, necessary) ( Order transaction date, length of 8 bytes, necessary) (Transaction type, length of 4 bytes, necessary) (Payment connection version, necessary) (URL of receiving background transactions, within 80 byts, necessary) 36 / 51 http://www.ChinaPay.com (URL of receiving page transaction, within 80 bytes, necessary) (Payment gateway number, optional) (Merchant private field, optional, within 60 bytes) (ASCII code of 256 bytes, necessary, digital signature of key data submitted by this transaction)
Explanation: PageRetUrl: URL of receiving page transaction, used to lead the user back to merchant website pages after payment. BgRetUrl: URL of receiving background transactions, used to record transaction and processing information, and it is invisible to user. Besides, ChinsaPay will judge whether need to retransmit the answer number in term of the http return code, in order to ensure the acceptance of background answer. The URL can not fill parameters. If you need to passing parameters, you can use" Priv1" field. Priv1: - is the private field for the Merchant , will be a part of the digital signature in payment version 20141120. Chinapay will return the copy of the field which merchant sent to Chinapay. No Chinese or special character is allowed in this field, based the requirement of digital signature. GateId: Optional, means payment gateway number, if it is GateId(payment gateway number), users directly enter payment webpage, if not, users enter gateway selection webpage. OrdId: means order number, The field can be customized by Merchant Orders uniqueness: ChinaPay According to MerId,OrderId and TransDate which include in the request form to determine the orders uniqueness. Refer to appendix B.  Digital Signature of Transaction Data Digital signature is required when Merchant sends transaction data to ChinaPay. For Version 20141120, signature data should use ―Function Sign - to generate digital signature for a string‖. Names of functions are: NetPayClient for Java :Sign(refer to Chapter 3.5.1) NetPayClient for Win32 :signData (refer to Chapter 3.4.2) NetPayClient for C :signData (refer to Chapter 3.4.3) NetPayClient for C# :Sign (refer to Chapter 3.4.4) NetPayClient for PHP :sign (refer to Chapter 3.4.45) Description: The digital signature in version 20141120 is to sign the strings, so the strings must be organized in a certain sequence as below: MerId OrdId TransAmt CuryId TransDate TransType 37 / 51 Version BgRetUrl PageRetUrl GateId Priv1 http://www.ChinaPay.com  Content of Receiving Transaction Data ChinaPay will send transaction response to merchant when the payment has been finished. Page receiving URL and background receiving URL will both receive transaction data including the following fields. Take page FORM data for example.(pay attention to the capital letters and small letters)
(‖action‖ is the URL of submitting transaction data)
 Description: ―status‖ represents the transaction statement, only when the value is ―1001‖ means successful transaction, other values means failure, so after verify the sign date was send by ChinaPay, you still need to judge the statement value is ―1001‖ please read the description carefully in Appendix B  Verifying Signature of Response Data After payment transaction is finished, ChinaPay will send result information to merchant, which can be received by both page receiving URL and background receiving URL. Merchant should verify its signature to confirm whether this response is sent by ChinaPay. ―Function check - to verify transaction response‖ should be used. Names of functions are: NetPayClient for Java NetPayClient for Win32 NetPayClient for C NetPayClient for C# NetPayClient for PHP :verifyTransResponse (refer to Chapter3.5.1) :check (refer to Chapter 3.4.2) :verifyTransResponse (refer to Chapter 3.4.3) :verifyTransResponse (refer to Chapter 3.4.4) :verifyTransResponse (refer to Chapter 3.4.45) 5. Refund 5.1. Object 38 / 51 http://www.ChinaPay.com Currently, ChinaPay employed plenty ways of refund, and this chapter mainly guide ChinaPay’s merchant members access through single refund method to refund system. facilitate online payment business for success by ChinaPay refund transactions. 5.2. Transaction Process After payment transition is finished, merchants can develop their refund transition payment service through payment gateway subsystem of payment service interfaceNetPayClient, according to the order forms generated by the results of payment transition. 【Step 1】Refund Confirmation 1. Merchants according to the situation of payment transition select the refund program, then generate refund order or the information of refund bill. 2. Merchants confirm the information of refund ,and start refund transition. 【Step 2】Refund Response 3. Merchants confirm the data of refund transition, and apply refunding to ChinaPay with the data form regulated by ChinaPay. At the same time, payment gateway check the validity of merchants. 4. After ChinaPay received refund order, it will send back merchants the response of ―Refund is accepted successfully.‖ At the same time. 5. The response of success/failed refund will be send to notice merchants through the URL which is written by merchants at the time of submitting refund information. 【Step 3】Refund Dispose 6. ChinaPay completes refund transition with bank, which has manual intervention process ,and will generate refund information at last. 7. Merchants can look over the process of refund and the information of refund result from console platform. 【Step 4】Refund Finished 8. The refund operation is finished. 5.3. Connecting Approaches 5.3.1. Connection URL Merchant can connect with ChinaPay’s enquiry system by the means of WEB service. URL of receiving transaction data is: Test Environment: http://payment-test.chinapay.com/refund1/SingleRefund.jsp Production Environment: http://console.chinapay.com/refund/SingleRefund.jsp 5.3.2. Version 5.3.2.1. Refund Version 20070129  Content Submitted on Single Refund Page Merchants submitted order information to ChinaPay’s payment connection URL Content of the FORM on enquiry page should include:
(‖action‖ is the URL of submitting enquiry data) (MerId is the Merchant ID assigned by ChinaPay, length of 15 bytes, necessary) 39 / 51 http://www.ChinaPay.com (Transaction Type: 0002 represents refund transaction) (Order ID, length of 16 bytes, necessary) (Amount of merchant refund, with 2 decimal,length of 12 bytes, necessary) (Transaction date of the particular order, length of 8 bytes, necessary) (Version of single enquiry, necessary) (URL of receiving refund status, optional, within 80 bytes) (Merchant’s reserve field,within 40 bytes, necessary, optional) (ASCII code of 256 bytes, necessary)
 Statement: TransType is transaction type, 0002 represents refund. ReturnURL is refund respond, whose content is optional. If merchants would like to get informed when the refund status changed, the files should be filled in. Priv1 is merchant’s private field, necessary, whose data is defined by merchant but should not be repeated. In order to avoid submitting refund request for several times, data in this field will be verified if it is repeated. If the refund request has been submitted before, it is considered that it has been received and will not be processed again  Digital Signature of Transaction Data Digital signature is required when Merchant sends transaction data to ChinaPay. For Version 20070129, signature data should use ―Function Sign - to generate digital signature for a string‖. Names of functions are: NetPayClient for Java NetPayClient for Win32 NetPayClient for C NetPayClient for C# NetPayClient for PHP :Sign (refer to Chapter3.5.1) :signData (refer to Chapter 3.4.2) :signData (refer to Chapter 3.4.3) :Sign (refer to Chapter 3.4.4) :sign (refer to Chapter 3.4.45)  Statement For Version 20070129, signature data uses ―Function Sign - to generate digital signature for a string‖, so merchants should contact stings follow some sequence, the sequence is as follows: MerID  TransDate TransType OrderId Content of Refund Response Data 40 / 51 RefundAmount Priv1 http://www.ChinaPay.com ChinaPay’s server program will send back ―refund request received‖ response to merchant after processing refund request. When the status of particular refund changes into success or failure, corresponding response will also be sent to merchant.  Format of ―success‖ response: ResponseCode=value0&MerID=value1&ProcessDate=value2&SendTime=value9&TransTyp e=value3&OrderId=value4&RefundAmout=value5&Status=value6&Priv1= value7&CheckValue=value8  Format of ―failure‖ response: ResponseCode=value0&Message=message_string   Statement: Merchant can judge whether the refund is successful via ResponseCode. ResponseCode value of 0 represents successful refund while other Response codes mean failed refund.  Definition of each field in ―success‖ response: ResponseCode : The code of response, the common value is 0(When the value is 0, it will has other field data sent back to check the signature of the message). MerID: Merchant ID, 15 bytes figure ProcessDate: ChinaPay’s process date, 8 bytes figure SendTime: Time of ChinaPay sending response code, 6 bytes figure(hhmmss), this field is not in digital signature TransType: Transaction type, 4 bytes figure OrderId: Original order ID, 16 bytes figure RefundAmout: Refund amount, 12 bytes figure Status: Status of particular refund, 1 byte figure 1 Refund request successfully 3 Refund is succeed 8 Refund is fail Priv1: Merchant’s private field, maximum 40 bytes Checkvalue: Signature verification, 256 bytes Definition of each field in ―failure‖ response: ResponseCode : Response code, 3 bytes figure Message: Explanation of response code  Signature Verification of Response Data Response data will be sent to merchant when the refund request is successfully submitted or the refund status changes into success or failure. After receiving response 41 / 51 http://www.ChinaPay.com data, merchant should verify the signature to confirm whether this data is sent by ChinaPay, using ―Function check - to verify transaction response‖. Names of functions are: NetPayClient for Java NetPayClient for Win32 NetPayClient for C NetPayClient for C# NetPayClient for PHP  :verifyAuthToken (refer to Chapter3.5.1) :checkData (refer to Chapter 3.4.2) :verifySignData (refer to Chapter 3.4.3) :verifyAuthToken (refer to Chapter 3.4.4) :verify (refer to Chapter 3.4.45) Statement: For Version 20070129, verifying digital signature of refund transaction should use ―Function check - to verify transaction response‖, and the strings should be linked by the following order: MerID ProcessDate TransType OrderId RefundAmount Status Priv1 6. Query 6.1. Object Every transaction submitted to ChinaPay can be inquired both on merchant console, and inquiry service. This chapter conducts merchant to set up connection with ChinaPay’s enquiry system, so that they can facilitate merchant to inquire transactions. 6.2. Transaction Process Merchant connect inquiry order information that meet merchant console according informative details of payment transition, then, they undertake the inquiry operation of transactional details. The processing flow of inquiry includes 【Step 1】Inquiry Confirmation 1. Merchant generates inquiry order information. 2. Merchant confirms inquiry order information, which should meet ChinaPay’s code requirement. 【Step 2】Inquiry Action 3. After confirming inquiry order, merchant applies to ChinaPay for inquiring transactional details with the data format regulated by ChinaPay. 4. ChinaPay deals with the inquiry of transactional details according to merchant’s information and inquiry order information submitted. 【Step 3】Inquiry Finished 5. ChinaPay’s server program send back the response of query results to merchant once it finished undertaking the request of querying transactional details. 6. Transactional details’ query finished 42 / 51 http://www.ChinaPay.com 6.3. Connection Approaches 6.3.1. Connection URL Merchant can connect with ChinaPay’s single enquiry system by the means of WEB service. URL of receiving transaction data is: Test Environment: http://payment-test.chinapay.com/QueryWeb/processQuery.jsp Production Environment: http://console.chinapay.com/QueryWeb/processQuery.jsp In addition, as we add extra note that ChinaPay adopts the way of flow control to permit merchant accessing to, following conditions should be satisfied:  Request will be responded only if it is submitted from IP address designated by merchant that has the right to inquire transaction, and the interval between two successful enquiries should be longer than the system’s set interval. Otherwise system will report ―illegal merchant request‖ (Error code 111).  Transactions of failure status which are inquired in a fix time should not exceed some volume, otherwise system will report ―over-flow control‖ (Error code 305). Therefore, when merchant applies for single enquiry function, its server’s IP address and Merchant ID should be provided. 6.3.2. Version 6.3.2.1. Enquiry Version 20060831(Single Query)  Content Submitted on Single Enquiry Page Merchant submits order information to ChinaPay’s payment connection URL. Content of the FORM on enquiry page should include:
(‖action‖ here is the URL of submitting enquiry data) (MerId is the Merchant ID assigned by ChinaPay, length of 15 bytes, necessary) (Transaction Type: 0001 represents consumption transaction) (Order ID, length of 16 bytes, necessary) (Transaction date of the particular order, length of 8 bytes, necessary) (Version of single enquiry, necessary) (Merchant’s reserve field) (ASCII code of 256 bytes, necessary)
 Digital Signature of Transaction Data Digital signature is required when merchant sends transaction data to ChinaPay. For Version 20060831, signature data should use ―Function Sign - to generate digital 43 / 51 http://www.ChinaPay.com signature for a string‖. Names of functions are: NetPayClient for Java :Sign (refer to Chapter 3.5.1) NetPayClient for Win32 :signData (refer to Chapter 3.4.2) NetPayClient for C :signData (refer to Chapter 3.4.3) NetPayClient for C# :Sign (refer to Chapter 3.4.4) NetPayClient for PHP :sign (refer to Chapter 3.5.5)  Statement: For Version 20060831, digital signature of enquiry transaction should use ―Function Sign - to generate digital signature for a string‖, and the strings should be linked by the following sequence: MerID  TransDate OrdId TransType Content of Query Response Data ChinaPay’s server program will send back the enquiry result to merchant after undertaking query request. Format of ―success‖ response(Note case sensitive): ResponeseCode=value1&merid=value2&orderno=value3&amount=value4¤cyc ode=value5&transdate=value6&transtype=value7&status=value8&checkvalue=value9 &GateId= value10&Priv1= value11 Format of ―failure‖ response(Note case sensitive): ResponeseCode=value0&Message=message_string  Statement: Merchant can judge whether the query is successful via ResponseCode. ResponseCode value of 0 represents successful query while other Response codes mean failed query. Definition of each field in ―success‖ response: ResponeseCode: Response code, successful value is 0 merid: Merchant ID, 15 bytes figure orderno: Enquiry Order ID, 16 bytes figure amount: Transaction amount, 12 bytes figure currencycode: Transaction currency, 3 bytes figure transdate: Transaction date, 8 bytes figure transtype: Transaction type, 4 bytes figure status: Transaction status, 4 bytes figure checkvalue: Digital signature, 256 bytes GateId: Transaction gateway ID, 4 bytes 44 / 51 http://www.ChinaPay.com Priv1: Merchant private field Definition of each field in ―failure‖ response: ResponeseCode: Response code, 3 bytes figure Message: Explanation of response code  Signature Verification of Response Data ChinaPay will send the enquiry information to merchant when completing enquiry transaction, using ―Function check - to verify transaction response‖. Names of functions are: NetPayClient for Java :verifyTransResponse (refer to Chapter 3.5.1) NetPayClient for Win32 :check (refer to Chapter 3.4.2) NetPayClient for C :verifyTransResponse (refer to Chapter 3.4.3) NetPayClient for C# :verifyTransResponse (refer to Chapter 3.4.4) NetPayClient for PHP :verifyTransResponse (refer to Chapter 3.4.45) Appendix A Common Connection Problems and Solutions 1. In the development process , reported 157 error code. QA: Check to see if GATEID is 0001, if it is, delete 0001 2. After payment online, how to do, if click submit button, the page presents “ Gateway Routing doesn’t exsit”? QA: Set GateId’s value to empty, and then to submit the order to ChinaPay. 3. After payment online, how to do, if click submit button, the page presents “ The standard data field cannot be blank”? QA: Merchant checks whether every piece of program is written according to <>. When come up with such report, it expresses program designer doesn’t meet with the manual, there are some stupid mistakes such as spelling mistake, forgetting to put in important data and so on. Remind merchant to check the parameters as follows: MerId, OrdId, TransAmt, CuryId, TransDate, TransType and some relative programs. Typical case: One company’s program’s designer input: …… …… The correct one is: . A word’s error contributes to the difficult of data reading. That is, function can’t find the important information included by curyId, which contributes to the report of ―Standard data field can not be blank!‖ 4. After payment online, how to do, if click submit button, the page presents “ The merchant’s code is empty”? QA: This problem mainly happened in UPOP, as the MerId has not been configured the Id used in UPOP. Merchants need to contact the operation center (phone NO.: 021-61871399) to configure this information. 45 / 51 http://www.ChinaPay.com 5. How to deal with the problem that the system report 500 error code during merchant’s testing process? QA: This error is systematic error, which belongs to the error of compiling program. That is because merchant mixed test submit URL and official submit URL. Typical case: When compile programs , designer input: ……
…… This is test merchant, so the right content after action is http://payment-test.chinapay.com/, that is to say, the right input is: 。 6. How to deal with the problem that merchant comes up with -109 error code? QA:-109 error code represents encryption is not successful, which may be caused by many problems. Currently, the main reason is that the signature method merchant used is not right, which result in fail signature. 7. How to deal with the problem that merchant comes to illegal length? QA: Illegal length is because of merchant’s wrong configuration that the length of parameters is not follow actual demands. For example ,OrderId is not 16 bytes,TransDate is not 8 bytes, TransAmt is not 12 bytes, Checkvalue is not generated, and so on, all of which may cause illegal length. The detail statement of sending parameters is as follows: String MerId – merchant ID, It is defined as a string with the length of 15 bytes that is assigned by ChinaPay or the clearing bank when the merchant agrees to use the service provided by ChinaPay. String OrdId – order number. It is specified as a 16-byte long numeric string that is generated by the merchant’s system, and previously failed transactions could be paid again. String TransAmt– transaction amount. This variable is defined as a numeric string and has the length of 12. For example, the string ―000000001234‖ represents 12.34RMB in this case. String CuryId – the type of the currency used. It is a string containing 3 bytes. Currently, only the value ―156‖ is accepted to represent RMB in the system. String TransDate– the date of the transaction. This numeric string is defined with the length of 8 to represent the transaction date with the format of YYYYMMDD. String TransType – the transaction type. It is a string sized 4 and values between ―0001‖ and ―0002‖. Hereinto, ―0001‖ represents payment transaction and ―0002‖ refers to refund transaction. Return Value String CheckValue - check value. It is the digital signature value with 256 bytes generated by ChinaPay based on the transaction results. 8. What’s the problem that ERRORCODE=110? 46 / 51 http://www.ChinaPay.com QA: Background return URL or Page return URL is too long. The length of Background return URL can’t over 80 bytes. If it is over 80 bytes ,the system will report 110 error code. Advice merchant alter Background return URL and Page return URL, limit the length within 80 bytes. 9. How to deal with the problem that AXTIVEX control can’t create object or DLL is not registered during the development process of ASP? QA: a) Let merchant to check whether the SCRIPT of system XP has been updated to the latest version. b) Let merchant to check whether lode CHINAPAY.DLL and CPNPC.DLL correctly, and put NETPAY.DLL on the SYSTEM32 folder. 10. What’s the problem that system reports illegal page in the development process? QA: Submit page should use popup windows. If merchant use frame interface, that the submission page will not redirect properly, that would report illegal page. Advice merchant to alter the structure of website, and to use popup windows instead of directing in the frame of page. 11. When sending transaction, some other error report information status code Transaction Description 1001 Purchase transaction succeeded 1003 Refund transaction succeeded 1005 Refund order cancel succeeded others All the other response codes refer to a failed transaction. Please check the detailed description from ChinaPay’s Merchant Management System or error information files of banks 12. During the system testing, successful payment but occur verifying signature mistake when return to merchant website page. QA: Firstly, the program developing must keep accord to the content of << NetPayClient User Manual>>. Typical Example: One company’s programmer input following content when testing company: …… Chkvalue = request.getparameter(―chkvalue‖) …… Because the sending parameter’s name is―ChkValue‖, when feedback fetch the ―ChkValue‖ too. In fact, this parameter should be ―checkvalue‖, so the transmit parameter value is null, and results to failure of verifying signature. That is to say: Chkvalue = request.getparameter(―checkvalue‖) This mistake as a result of the merchant didn’t code the program according to << NetPayClient User Manual >>. 13. What should we do when the failure of initializing public key occurs? QA: If merchants develop their program in JAVA, please check that whether merchants have input the public key number instead of merchant ID. 47 / 51 http://www.ChinaPay.com Typical Example: One company’s programmer input following content when testing company: …… Flag=key.buildKey(―808080002100999‖,0‖c:\winnt\\PgPubk.key‖); …… But, the correct code should like this: …… Flag=key.buildKey(―999999999999999‖,0‖c:\winnt\\PgPubk.key‖); …… 14. What we should do when the -118 mistake occurs? QA: Generally speaking, this mistake does not occur frequently. It is mainly because the merchant use the incorrect private key or transmit the wrong parameters to verifying signature method which lead to verify signature error. For example, the testing merchant use the producing merchant’s private key or signature method lead to incorrectly parameter transmitting and verifying signature failure. Typical Example: One merchant use producing public key when test testing online system, result to -118 mistake, after modified to testing merchant public key the error removed. 15. What about can’t receive the background answer? QA: Checking that whether the response acceptance code have something wrong with the judgment which responsible for judging the qualification of accepting response; and ensure the correct accepting response URL when sending transaction. 16. How to inform ChinaPay when accept background response successfully? QA: WEBSEVER feedback automatically, generally, successfully acceptance will return number 200 automatically, so merchant don’t need any parameter. Only when the value of OrderStatus is ―1001‖ means successful transaction, the rest values all mean failing transaction. And merchant need to judge this then adds to own database. 17. What about the failure of loadlib(CHINAPAY.DLL)? QA: Netpay.dll must be put in the system32 folder. Appendix B The Instructions for Payment Interfaces 1. Response for payment results from ChinaPay BgRetUrl: URL of receiving background transactions, necessary. It is used to receive the payment results sent by ChinaPay when cardholders didn’t return to merchant’s website after paying successfully on the online banking page. The address is suggested to use the ip address instead of domain name, and external network must be able to access, while can’t fill any parameters. Otherwise, it’ll affect merchants receiving ChinaPay’s background response. If merchants need to transfer parameters, they could make full use of Priv1, whose length is limited to 60 bytes. Before putting the payment interface into operation formally, merchants must test whether the BgRetUrl can normally receive ChinaPay’s response. 48 / 51 http://www.ChinaPay.com The digital signature of the payment response message have to be verified by the m erchant. The only status indicates payment successful is 1001, all other statuses are reco gnized as unsuccessful. Meanwhile, the merchant must compare the content of the respo nse message with the transaction data in its system. The message from Chinapay should be the only reference if there was a difference. ChinaPay has two payment results notifications, and the background response has retransmission mechanism, so merchants’ system must judge whether the order is repeatable before modifying the order’s status in merchants’ database. 2. Priv1: Merchant private field ChinaPay fulfills the same content that merchants send to ChinaPay in this field, and returns to merchants. This field does not support Chinese and special characters, which will affect the signature. So the merchants must limit the input type of this field, and prevent the cardholders inputting Chinese characters or other special characters. 3. Merchant web page tips  Suggest cardholders use IE browser;  Suggest cardholders following the page prompts jump back to the merchant site after paying successfully on the online banking page so as to ensure the merchant’s system receiving payment results in time ;  Suggest cardholders finish payment operation after ordering as soon as possible. 4. Merchant change tips If there are changes in merchant’s server, here are a couple of things to be aware: 1) If the domain name changes, merchants need to consider updating the following information:  PageRetUrl and BgRetUrl in payment interface;  Notification addresses in settlement reconciliation and settlement account interfaces. Merchants should contact the operation center (phone NO.: 021-61871399) to bind new addresses, which will take effect in the next day. 2) If IP address changes, merchants need to consider updating the following information:  PageRetUrl and BgRetUrl in payment interface; Ip addresses bound in ChinaPay where merchants launch single query request in single query interface. Merchants should contact the operation center (phone NO.: 021-61871399) to bind new ip addresses, which will take effect in the next day.  Notification addresses in settlement reconciliation and settlement account interfaces. Merchants should contact the operation center (phone NO.: 021-61871399) to bind new addresses, which will take effect in the next day. Description of Orders uniqueness Notice: The MerId(Merchant Id), OrderId and TransDate which include in the request Form to determine the orders uniqueness. eg. Use the same MerId and OrderId,but difference TransDate to request the payment, It will be considered as same Order.  5. Appendix C Response Code Description 49 / 51 http://www.ChinaPay.com 1. ChinaPay transaction status code Form 3 ChinaPay transaction status code status code Transaction Description 1001 Purchase transaction succeeded 1003 Refund transaction succeeded 1005 Refund order cancel succeeded others All the other response codes refer to a failed transaction. Please check the detailed description from ChinaPay’s Merchant Management System or error information files of banks 2. NetPayClient API Error Codes Form 4 NetPayClient API Error Codes status code Status Information All methods -111 Private key path is not set, or NPCDIR environment variable is not set Signature methods -100 NPCDIR environment variable is not set -101 Merchant private key file does not exist or can’t be opened -102 private key file format error -103 private key merchant id is not compatible with signature merchant id -109 Checking the merchant’s signature failure -130 Length of string for signature is blank Signature verification methods -112 ChinaPay public key file does not exist or can’t be opened -113 Public key file format error -114 Public key file error -118 Signature verification failure -134 Public key file path set error 3. Query,Single Refund Error Codes ERROR CODE ERROR MESSAGE 101 Merchant id error or is blank 102 Order number of transaction response inquiry is blank 103 Transaction date is blank 104 Request transaction type error 105 Merchant id length error 106 Order number length error 107 Transaction date length error 108 Transaction type is blank or length error 50 / 51 http://www.ChinaPay.com 109 Version number is blank 110 Version number error 111 Merchant request forbidden 112 Transaction type error 116 Amount is blank 117 Merchant private field length error 118 Signature field error 120 Accumulated refund amount is over original payment amount 121 Refund amount does not equal to original order amount 122 Refund amount should be less than original order amount 123 Total refund amount is more than original order amount 201 Plaintext data is blank 201 Signature data does not exist 202 Signature error 203 Signature verification failure 204 Signature verification data error 205 Repeat submitting the transaction 301 Inquired transaction does not exist 302 Inquiry database error 303 Response data package error 304 Response data string transformation error 305 Exceed volume control range 307 Corresponding data is not found 402 Original transaction doesn’t exist. The transaction date in the refund request should be the date when the payment transaction happened. 404 Other internal errors 51 / 51

Source Exif Data:
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : No
Page Count                      : 51
Language                        : zh-CN
Tagged PDF                      : Yes
Title                           : ChinaPay NetPayClient API  Merchant Manual
Author                          : Green.li
Subject                         : Version 2.5.17
Creator                         : Microsoft® Office Word 2007
Create Date                     : 2014:12:15 03:14:29
Modify Date                     : 2014:12:15 03:14:29
Producer                        : Microsoft® Office Word 2007
EXIF Metadata provided by EXIF.tools

Navigation menu