faizah

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 1
51200 Kuala Lumpur

revPAY Merchant API

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 2
51200 Kuala Lumpur

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 3
51200 Kuala Lumpur

Table of Contents

Table of Contents.............................................................................................................................................................. 3
1. Introduction .............................................................................................................................................................. 6
1.1 Purpose ................................................................................................................................................................. 6
1.2 Audience ............................................................................................................................................................... 7
1.3 Integration Process Checklist ................................................................................................................................ 7
1.4 Payment Process Flow .......................................................................................................................................... 8
1.5 Re-query Payment Status Flow ............................................................................................................................. 9
2. Technical Requirement ........................................................................................................................................... 10
2.1 Payment Request Parameters (Merchant to revPAY) ........................................................................................ 10
2.2 Payment Request Parameters (Merchant to revPAY) – JSON Format................................................................ 13
2.3 Sample HTML Source Code (Payment Request) ................................................................................................. 14
2.4 Payment Response Parameters (revPAY to Merchant) – Frontend ................................................................... 15
2.5 Sample HTML Source Code (Payment Response Frontend) ............................................................................... 17
2.6 Payment Response Parameters (revPAY to Merchant) – Backend..................................................................... 19
2.7 Sample PHP Source Code (Payment Response Backend) ................................................................................... 21
2.8 Re-query Payment Status Parameters (Merchant to revPAY) ............................................................................ 23
2.9 Re-query Payment Status Parameters (Merchant to revPAY) – JSON................................................................ 27
2.10 Re-query Fx Rate Parameters (Merchant to revPAY).......................................................................................... 28
2.11 Merchant (eCommerce Marketplace) Settlement Release Parameters (Merchant to revPAY)......................... 30
2.12 Payment Cancellation Request Parameters (Merchant to revPAY).................................................................... 32
2.13 Pre-Auth Cancellation Request Parameters (Merchant to revPAY) ................................................................... 34
2.14 Refund Request Parameters (Merchant to revPAY) ........................................................................................... 36
2.15 Customer Card Enrolment Request Parameters (Merchant to revPAY)............................................................. 38
2.16 Customer Card Enrolment Request Parameters (Merchant to revPAY) - JSON ................................................. 40
2.17 Customer Card Enrolment Response Parameters (revPAY to Merchant) - Fronted........................................... 41
2.18 Customer Card Enrolment Response Parameters (revPAY to Merchant) - Backend.......................................... 43
2.19 Pre-Auth Request Parameters (Merchant to revPAY) ........................................................................................ 45
2.20 Pre-Auth Response Parameters (revPAY to Merchant) – Frontend ................................................................... 47
2.21 Pre-Auth Response Parameters (revPAY to Merchant) – Backend..................................................................... 48
2.22 Pre-Auth Completion Request Parameters (Merchant to revPAY) - Backend.................................................... 50
2.23 Installment List Request Parameters (Merchant to revPAY) - Backend ............................................................. 52
2.24 Installment Request Parameters (Merchant to revPAY)..................................................................................... 55
2.25 Installment Response Parameters (revPAY to Merchant) – Frontend ............................................................... 57

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 4
51200 Kuala Lumpur

2.26 Installment Response Parameters (revPAY to Merchant) – Backend................................................................. 59
3. Security Control....................................................................................................................................................... 61
3.1 Electronic Signature ............................................................................................................................................ 61
3.2 Signature for Payment Request .......................................................................................................................... 62
3.3 Signature for Payment Response........................................................................................................................ 62
3.4 Signature for Re-query Payment Status Request ............................................................................................... 63
3.5 Signature for Re-query Payment Status Response ............................................................................................. 63
3.6 Signature for Re-query Fx Rate Request ............................................................................................................. 64
3.7 Signature for Re-query Fx Rate Response........................................................................................................... 64
3.8 Signature for Merchant Settlement Release Request ........................................................................................ 65
3.9 Signature for Merchant Settlement Release Response ...................................................................................... 65
3.10 Signature for Payment Cancellation Request ..................................................................................................... 66
3.11 Signature for Payment Cancellation Response................................................................................................... 66
3.12 Signature for Pre-Auth Cancellation Request ..................................................................................................... 67
3.13 Signature for Pre-Auth Cancellation Response................................................................................................... 67
3.14 Signature for Refund Request............................................................................................................................. 68
3.15 Signature for Refund Response .......................................................................................................................... 68
3.16 Signature for Customer Card Enrolment Request .............................................................................................. 69
3.17 Signature for Customer Card Enrolment Response ............................................................................................ 69
3.18 Signature for Pre-Auth Request .......................................................................................................................... 70
3.19 Signature for Pre-Auth Response........................................................................................................................ 70
3.20 Signature for Pre-Auth Completion Request ...................................................................................................... 71
3.21 Signature for Pre-Auth Completion Response.................................................................................................... 71
3.22 Signature for Installment List Request................................................................................................................ 72
3.23 Signature for Installment List Response ............................................................................................................. 72
3.24 Signature for Installment Request ...................................................................................................................... 73
3.25 Signature for Installment Response.................................................................................................................... 73
3.26 Sample Signature Generation ............................................................................................................................. 74
4. Frequency Asked Questions (FAQ).......................................................................................................................... 75
4.1 FAQ...................................................................................................................................................................... 75
5. Contact Information................................................................................................................................................ 80
5.1 System Integration.............................................................................................................................................. 80
5.2 Customer Care .................................................................................................................................................... 80
5.3 Operation ............................................................................................................................................................ 80

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 5
51200 Kuala Lumpur

5.4 Settlement........................................................................................................................................................... 80
5.5 Business............................................................................................................................................................... 81
6. Payment Flow.......................................................................................................................................................... 82
6.1 FPX Payment Flow............................................................................................................................................... 82
6.2 Visa Master Payment Flow.................................................................................................................................. 84
6.3 UnionPay Payment Flow ..................................................................................................................................... 85
6.4 Merchantrade Money Payment Flow ................................................................................................................. 87
6.5 Alipay Online Payment Flow ............................................................................................................................... 88
6.6 Boost Payment Flow ........................................................................................................................................... 90
6.7 TnGo Payment Flow ............................................................................................................................................ 91
6.8 MBB QR Payment Flow ....................................................................................................................................... 92
7. System Integration.................................................................................................................................................. 93
7.1 Pre-requisite........................................................................................................................................................ 93
7.2 Test Cases............................................................................................................................................................ 93
7.3 Test Result........................................................................................................................................................... 93
7.4 Sign Off Letter ..................................................................................................................................................... 93
Appendix ......................................................................................................................................................................... 94
Appendix A: Payment ID Details ..................................................................................................................................... 94
Appendix B: Bank Code Details ....................................................................................................................................... 95
Appendix C: Payment Response Code Details ................................................................................................................ 97
Appendix D: Key_Index Details ..................................................................................................................................... 101
Appendix E: eCommerce Marketplace Details ............................................................................................................. 102
Appendix F: Billing_Address / Shipping_Address Details.............................................................................................. 103
Appendix G: Transaction_Type Details ......................................................................................................................... 103
Appendix H: Card_Type Details..................................................................................................................................... 103
Appendix I: Card_Category Details ............................................................................................................................... 103
Appendix J: Card_Brand Details.................................................................................................................................... 104

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 6
51200 Kuala Lumpur

1. Introduction

Revenue payment gateway, a revPAY Technology, is a payment processor which provides payment solutions to
e-commerce platforms or existing payment gateways to accept multiple payment products with multi currencies.

1.1 Purpose

The document provides technical information on integrating in between merchant’s e-commerce
platform/Payment Gateways and revPAY Payment Processor.

Transactions features include:

1. Foreground processing or Background processing – for an e-commerce platform, which is normally
integrated in foreground processing mode, which revPAY will be performing the payment information
capturing and payment processing with schemes, allowing e-commerce platform to have minimum
development over the payment logic.

However, for other e-commerce platforms, such as payment gateways, which already have its own payment
capturing and processing logics, revPAY will provide Background Processing Mode to payment gateways to
route transaction authorization via revPAY as back end processor.

2. Retails Mode – One Time Payment.

3. Multi Currencies – Multiple Currencies allowed a customer to choose to perform payment.

4. Transaction types:

a. Basic: Payment and Re-query only.

b. Tokenization: Customer Card Enrolment, Payment and Re-query.

c. Online Booking (E.g: Hotel): Pre-Auth and Pre-Auth Completion.

d. Cancel Payment: Payment Cancellation (Void), Pre-Auth Cancellation, and Refund.

e. Easy Payment Plan (EPP): Installment.

f. Others: Re-query Fx Rate and Marketplace Settlement Release.

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API
Wisma Revenue
No 12, Jalan Udang Harimau 2, Date: 16 Jul 2021 Version: 1.41
Kepong Business Park,
51200 Kuala Lumpur Page 7

1.2 Audience

Web Developers and Project Managers.

1.3 Integration Process Checklist

During the integration process, merchants can refer to below checklist to complete the integration process.

1) Before the integration process can start, refer to the following table, kindly provide following 3 URLs and
your timeline to us:

No Item Description

01 Integration Receive email with merchant’s ID, registered name, trading name, payment URL, Re-query URL,
credentials merchant portal URL, email & password, merchant keys, test cards and test cases.

02 Website URL URL for the company website.

03 Return URL URL for the user to be redirected after the transaction is completed. (E.g. receipt page).

04 Backend URL URL to return the transaction result via server to server. Ensure URL provided is HTTPs.

05 Timeline UAT testing timeline for integration.

2) After the Integration testing process is complete, below are the steps for completion.

No Item Description

01 Submit Test Results Merchants to email test results (including transaction process print screen) to
[email protected] for checking. Email will be reverted once test results are
verified.

02 Production Details After test results are verified and passed, revPAY team will email the production details for
Email merchant migrate to Live.

03 Settlement Report Merchant can download daily settlement report via revPAY Merchant Portal. User account
details will be provided by revPAY team via email after sign-off.

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API
Wisma Revenue
No 12, Jalan Udang Harimau 2, Date: 16 Jul 2021 Version: 1.41
Kepong Business Park,
51200 Kuala Lumpur Page 8

1.4 Payment Process Flow

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API
Wisma Revenue
No 12, Jalan Udang Harimau 2, Date: 16 Jul 2021 Version: 1.41
Kepong Business Park,
51200 Kuala Lumpur Page 9

1.5 Re-query Payment Status Flow

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API
Wisma Revenue
No 12, Jalan Udang Harimau 2, Date: 16 Jul 2021 Version: 1.41
Kepong Business Park,
51200 Kuala Lumpur Page 10

2. Technical Requirement

2.1 Payment Request Parameters (Merchant to revPAY)

The input definition represents the required input parameters from the Merchant site and end user. Merchant
needs to submit basic transaction information such as amount and transaction description to revPAY for
processing. User will be redirected to payment window to enter additional details such as credit/debit card or
etc and proceed with payment.

All transactions will be performed over an SSL/HTTPS channel between the user and the revPAY, merchant and
revPAY. Once the transaction is complete, the user is routed back to the Merchant site.

Assumptions

All requests are sent to revPAY via the HTTPS POST/GET or JSON Method. Merchants are required to send all
transaction requests to the following URL (confirm with revPAY administrator for the latest URL):

Environment:

https://

If there is validation error, user is routed back to Merchant site. Else, user is routed to payment window. Users
must enter user payment detail and submit request to revPAY. Merchants and users are required to supply the
required amount of input parameters. Any requests containing the incorrect amount of parameters will be
rejected.

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 11
51200 Kuala Lumpur

Merchant HTTPS POST payment request parameters to revPAY Payment Gateway

No Field Name Data Type (Size) M/O Description

1 Revpay_Merchant_ID Alpha-numeric (50) M Unique merchant account number as
assigned by revPAY.
2 Payment_ID Integer (3) M Payment method. (See Appendix A)
3 Bank_Code Alpha-numeric (20) O Bank code. (See Appendix B)
4 Reference_Number Alpha-numeric (50) M Merchant Reference Number of the order
that uniquely identifies the transaction in
5 Amount Numeric (12) M the merchant’s system.
Amount must be entered with the
6 Currency Alphabet (3) M decimal point.
Following ISO 4217 currency codes.
7 Transaction_Description Alpha-numeric (200) M Merchants may supply additional
messages to provide a description of the
8 Billing_Address Alpha-numeric (999) O transaction. This value will be displayed in
9 Shipping_Address the merchant transaction listing report.
10 Device_ID Alpha-numeric (999) O Merchant to provide base on customer
11 Ecomm_Marketplace request in JSON format. (See Appendix F)
Alpha-numeric (64) C Merchant to provide base on customer
12 Promo_Code Alpha-numeric O request in JSON format. (See Appendix F)
(2048) Customer mobile/tablet device details.
Merchant to provide vendors details base
Alpha-numeric (50) O on goods selected by customer in JSON
format. (See Appendix E)
13 Transaction_Type Alpha-numeric (2) C Merchant’s promotion code and currently
revPAY keep this value as record purpose
14 Customer_ID Alpha-numeric (30) C only.
15 Customer_Name Alpha-numeric (50) O Merchant to provide transaction type
16 Customer_Email Alpha-numeric (200) O details. (See Appendix G)
Customer’s member/wallet ID.
17 Customer_Contact Alpha-numeric (20) O Customer name.
18 Customer_IP Alpha-numeric (100) M Customer email for receiving payment
19 Geo_Location Alpha-numeric (50) O status.
Customer contact number.
20 Card_Type Alpha-numeric (3) C Customer IP Address.
21 Card_Holder_Name Alpha-numeric (50) C Merchant to provide customer’s location
22 Funding_Pan Numeric (20) C to revPAY. It is for mobile/tablet user
which is have GPS feature.
23 Funding_Exp_Date Numeric (6) C Format: “(lat, lon)”
Customer’s card type. (See Appendix H)
24 Funding_CVV Numeric (4) C Customer’s name on the credit card.
Customer’s card account number.
Acceptable types are integers only
(without any special characters).
Customer’s card expiration year and
month. Acceptable types are integers
only. Format: YYYYMM
Customer’s card code value. Acceptable
types are integers only. 3 digits for
Visa/MasterCard. 4 digits for AMEX.

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 12
51200 Kuala Lumpur

25 Card_Issuer_Bank_Coun Alpha (3) C Issuer bank’s country code. Following ISO
C 3166-3 country codes.
try_Code C Required when Customer chooses specific
C payment method. (eg: Easy Payment Plan)
26 Installment_Plan Alpha-numeric (20) C Required when Customer chooses specific
payment method. (eg: Easy Payment Plan)
27 Installment_Term Alpha-numeric (20) Customer’s card tokenization reference
number.
28 Token_Pan Alpha-numeric (50) Customer’s card tokenization account
expiration year and month. Format:
29 Token_Exp_Date Numeric (6) YYYYMM
The index of key provided by revPAY to
30 Key_Index Integer (3) M encrypt the signature. (See Appendix D)
31 Signature SHA512 checksum signature. (See
32 Return_URL Alpha-numeric (128) M Electronic Signature)
Merchant URL that the user should be
Alpha-numeric (200) M redirected to after the transaction is
processed.

Note:
M : Mandatory field.

O : Optional field, value can be empty but parameter must exist.

C : Condition field.

UAT URL
HTML Format: https://staging-gateway.revpay.com.my/payment
JSON Format: https://staging-gateway.revpay.com.my/payment_json

Production URL
HTML Format: https://gateway.revpay.com.my/payment
JSON Format: https://gateway.revpay.com.my/payment_json

*Please choose JSON format for those apply Alipay Online (Mini Program)

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 13
51200 Kuala Lumpur

2.2 Payment Request Parameters (Merchant to revPAY) – JSON Format

Merchant send payment request parameters to revPAY Payment Gateway via JSON format.

Request

URL : {BaseURL}/payment_json

Method : HTTPS POST

Request Body :

{
"Revpay_Merchant_ID" : "MER00000000001",
"Payment_ID" : 2,
"Bank_Code" : "",
"Reference_Number" : "RF201774111",
"Amount" : 52.40,
"Currency" : "MYR",
"Transaction_Description" : "Order Number : Buy Power Bank",
"Billing_Address" : "",
"Shipping_Address" : "",
"Device_ID" : "",
"Ecomm_Marketplace" : "",
"Promo_Code" : "",
"Transaction_Type" : "",
"Customer_ID" : "",
"Customer_Name" : "John Doe",
"Customer_Email" : "[email protected]",
"Customer_Contact" : "0123456789",
"Customer_IP" : "121.121.118.2",
"Geo_Location" : "(3.1925996, 101.6590715)",
"Card_Type" : "",
"Card_Holder_Name" : "",
"Funding_Pan" : "",
"Funding_Exp_Date" : "",
"Funding_CVV" : "",
"Card_Issuer_Bank_Country_Code" : "",
"Installment_Plan" : "",
"Installment_Term" : "",
"Token_Pan" : "",
"Token_Exp_Date" : "",
"Key_Index" : 1,
"Signature" :
"0716dc1863519f53d47a11ec603d402782222083b2178f596d210fcb93287e81412dd529fa2adddd8e0cdfa2ddf0
bb5e8421f55a105196d4ee58961b253b98a1",
"Return_URL" : "https://devwebsite.revpay.com.my/return"
}

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 14
51200 Kuala Lumpur

2.3 Sample HTML Source Code (Payment Request)

Below is basic sample code payment request message from merchant.

<form method="post" action="https://staging-gateway.revpay.com.my/payment" accept-charset="UTF-8">

<input type="text" name="Revpay_Merchant_ID" value="MER00000000001"><br></br>
<input type="text" name="Payment_ID" value="2"><br></br>
<input type="text" name="Bank_Code" value=""><br></br>
<input type="text" name="Reference_Number" value="RF201774111"><br></br>
<input type="text" name="Amount" value="52.40"><br></br>
<input type="text" name="Currency" value="MYR"><br></br>
<input type="text" name="Transaction_Description" value="Order Number : Buy Power Bank"><br></br>
<input type="text" name="Billing_Address" value=""><br></br>
<input type="text" name="Shipping_Address" value=""><br></br>
<input type="text" name="Device_ID" value=""><br></br>
<input type="text" name="Ecomm_Marketplace" value=""><br></br>
<input type="text" name="Promo_Code" value=""><br></br>
<input type="text" name="Transaction_Type" value=""><br></br>
<input type="text" name="Customer_ID" value=""><br></br>
<input type="text" name="Customer_Name" value="John Doe"><br></br>
<input type="text" name="Customer_Email" value="[email protected]"><br></br>
<input type="text" name="Customer_Contact" value="0123456789"><br></br>
<input type="text" name="Customer_IP" value="121.121.118.2"><br></br>
<input type="text" name="Geo_Location" value="(3.1925996, 101.6590715)"><br></br>
<input type="text" name="Card_Type" value=""><br></br>
<input type="text" name="Card_Holder_Name" value=""><br></br>
<input type="text" name="Funding_Pan" value=""><br></br>
<input type="text" name="Funding_Exp_Date" value=""><br></br>
<input type="text" name="Funding_CVV" value=""><br></br>
<input type="text" name="Card_Issuer_Bank_Country_Code" value=""><br></br>
<input type="text" name="Installment_Plan" value=""><br></br>
<input type="text" name="Installment_Term" value=""><br></br>
<input type="text" name="Token_Pan" value=""><br></br>
<input type="text" name="Token_Exp_Date" value=""><br></br>
<input type="text" name="Key_Index" value="1"><br></br>
<input type="text" name="Signature"
value="0716dc1863519f53d47a11ec603d402782222083b2178f596d210fcb93287e81412dd529fa2adddd8e0cdfa
2ddf0bb5e8421f55a105196d4ee58961b253b98a1"><br></br>
<input type="text" name="Return_URL" value="https://devwebsite.revpay.com.my/return"><br></br>
<input value="Submit" type="submit">

</form>

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 15
51200 Kuala Lumpur

2.4 Payment Response Parameters (revPAY to Merchant) – Frontend

Merchants will receive the HTTPS POST/JSON response from revPAY after the payment is completed.
revPAY will use the values in the parameter “Return_URL” which is provided by the Merchant during the payment
request, as a location to return these payment results to. revPAY will respond these transaction results to
merchant’s “Return_URL” through the redirect method (Browser to Browser).

Every payment response message will include a Signature value for indefinite message content to be valid.
Merchant is strongly recommended to generate a Signature value based on the format given in 3.3 Signature for
Payment Response for matching purposes.

No Field Name Data Type (Size) M/O Description

1 Revpay_Merchant_ID Alpha-numeric (50) M Unique merchant account number as

assigned by revPAY.

2 Payment_ID Integer (3) M Payment method. (See Appendix A)

3 Bank_Code Alpha-numeric (20) O Bank code (See Appendix B)

4 Transaction_ID Alpha-numeric (50) M Payment Transaction ID generated by

revPAY.

5 Reference_Number Alpha-numeric (50) M Merchant Reference Number of the order

that uniquely identifies the transaction in

the merchant’s system.

6 Bank_Reference_Numb Alpha-numeric (50) O Bank/Scheme Reference Number of the

er order that uniquely identifies the transaction

in the bank’s system.

7 Amount Numeric (12) M Payment amount.

8 Currency Alphabet (3) M Payment currency

9 Transaction_Description Alpha-numeric (200) M Merchant transaction description.

10 Ecomm_Marketplace Alpha-numeric O Merchant ecommerce marketplace details.

(2048) (See Appendix E)

11 Promo_Code Alpha-numeric (50) O Merchant’s promotion code and currently

revPAY keep this value as record purpose

only.

12 Funding_Pan_Mask Alpha-numeric (20) O Customer’s card account number with

masking. System will share the number with

first 6 and last 4 digits in clear, the rests are

marked with “*”. E.g: 484281******7590

13 Funding_Bin Numeric (6) O Customer’s card bin.

14 Funding_Exp_Date Numeric (6) O Customer’s card expiration year and month.

Format: YYYYMM

15 Token_Pan Alpha-numeric (50) C Customer’s card tokenization reference

number.

16 Token_Exp_Date Numeric (6) C Customer’s card tokenization account

expiration year and month. Format:

YYYYMM

17 Fraud_Score Numeric (12) O Fraud Scoring of the transaction.

18 Response_Code Alpha-numeric (6) M Payment status code. (See Appendix C)

19 Error_Description Alpha-numeric (100) O Payment status description.

20 Settlement_Amount Numeric (12) O Payment settlement amount.

21 Settlement_Currency Alpha-numeric (3) O Payment settlement currency.

22 Settlement_FX_Rate Numeric (12) O Payment settlement in FX rate.

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 16
51200 Kuala Lumpur

23 Key_Index Integer (3) M The index of key provided by revPAY to
encrypt the signature. (See Appendix D)
24 Signature Alpha-numeric (128) M SHA512 checksum signature. (See Electronic

Signature)
25 Request_Datetime M
26 Response_Datetime Datetime M Payment request datetime.
27 Bank_Redirect_URL Datetime C Payment response datetime.
Alpha-numeric Bank/Scheme payment request URL. It is
(2048) only apply for Alipay Online (Mini Program).

Note:
M : Mandatory field

O : Optional field, value can be empty but parameter must exists

C : Condition field







































REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 36
51200 Kuala Lumpur

2.14 Refund Request Parameters (Merchant to revPAY)

Merchant HTTPS POST refund request parameters to revPAY Payment Gateway.

No Field Name Data Type (Size) M/O Description

1 Revpay_Merchant_ID Alpha-numeric (50) M Unique merchant account number as
assigned by revPAY.
2 Reference_Number Alpha-numeric (50) M Merchant unique Reference_Number of
the request for refund.
3 Original_Reference_Nu Alpha-numeric (50) M Original Reference_Number use for
request refund.
mber C Ecomm_Marketplace values - RefNo.
Original SubMerchant’s
4 Original_RefNo Alpha-numeric (50) Reference_Number use for request
refund.
5 Refund_Amount Numeric (12) M Merchant request refund amount.
6 Key_Index Integer (3) M The index of key provided by revPAY to
encrypt the signature. (See Appendix D)
7 Signature Alpha-numeric (128) M SHA512 checksum signature. (See
Electronic Signature)

Note:
M : Mandatory field

O : Optional field, value can be empty but parameter must exists

C : Condition field

UAT URL
HTML Format: https://staging-gateway.revpay.com.my/refund
JSON Format: https://staging-gateway.revpay.com.my/refund_json

Production URL
HTML Format: https://gateway.revpay.com.my/refund
JSON Format: https://gateway.revpay.com.my/refund_json

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 37
51200 Kuala Lumpur

*revPAY response in JSON format to merchant instantly.

No Field Name Data Type (Size) M/O Description

1 Revpay_Merchant_ID Alpha-numeric (50) M Unique merchant account

number as assigned by revPAY.

2 Transaction_ID Alpha-numeric (50) M Payment Transaction ID

generated by revPAY.

3 Reference_Number Alpha-numeric (50) M Merchant unique

Reference_Number of the

request for refund.

4 Original_Reference_ Alpha-numeric (50) M Original Reference_Number use

Number for request refund.

5 Original_RefNo Alpha-numeric (50) C Ecomm_Marketplace values -

RefNo. Original SubMerchant’s

Reference_Number use for

request refund.

6 Refund_Amount Numeric (12) M Merchant request refund

amount.

7 Amount_Balance Numeric (12) M Merchant transaction balance

after deduct any successful

refund.

8 Response_Code Alpha-numeric (6) M Payment status code. (See

Appendix C)

9 Error_Description Alpha-numeric (100) O Payment status description.

10 Key_Index Integer (3) M The index of key provided by

revPAY for use to encrypt

signature. (See Appendix D)

11 Signature Alpha-numeric (128) M SHA512 checksum signature.

(See Electronic Signature)

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 38
51200 Kuala Lumpur

2.15 Customer Card Enrolment Request Parameters (Merchant to revPAY)

Merchant HTTPS POST enrolment request parameters to revPAY Payment Gateway

No Field Name Data Type (Size) M/O Description

1 Revpay_Merchant_ID Alpha-numeric (50) M Unique merchant account number as
assigned by revPAY.
2 Reference_Number Alpha-numeric (50) M Merchant Reference Number of the order
that uniquely identifies the transaction in
3 Amount Numeric (12) M the merchant’s system.
Amount must be entered with the
4 Currency Alphabet (3) M decimal point.
5 Device_ID Alpha-numeric (64) C Following ISO 4217 currency codes.
6 Customer_ID Alpha-numeric (30) C Customer mobile/tablet device details.
7 Customer_Name Alpha-numeric (50) O Customer’s member/wallet ID.
8 Customer_Email Alpha-numeric (200) O Customer name.
Customer email for receiving payment
9 Customer_Contact Alpha-numeric (20) O status.
10 Geo_Location Alpha-numeric (50) C Customer contact number.
Merchant to provide customer’s location
11 Card_Type Alpha-numeric (3) C to revPAY. It is for mobile/tablet user
12 Card_Holder_Name Alpha-numeric (50) C which is have GPS feature.
13 Funding_Pan Numeric (20) C Format: “(lat, lon)”
Customer’s card type. (See Appendix H)
14 Funding_Exp_Date Alpha-numeric (6) C Customer’s name on the credit card.
Customer’s card account number.
15 Funding_CVV Numeric (4) C Acceptable types are integers only
(without any special characters).
16 Card_Issuer_Bank_Coun Alpha (3) C Customer’s card expiration year and
M month. Acceptable types are integers
try_Code only. Format: YYYYMM
Customer’s card code value. Acceptable
17 Key_Index Integer (3) types are integers only. 3 digits for
Visa/MasterCard. 4 digits for AMEX.
18 Signature Alpha-numeric (128) M Issuer bank’s country code. Following ISO
3166-3 country codes.
19 Return_URL Alpha-numeric (200) M The index of key provided by revPAY to
encrypt the signature. (See Appendix D)
20 Backend_URL Alpha-numeric (200) M SHA512 checksum signature. (See
Electronic Signature)
Merchant URL that the user should be
redirected to after the transaction is
processed.
revPAY will send transaction result to
Merchant via server to server.

Note:
M : Mandatory field

O : Optional field, value can be empty but parameter must exists

C : Condition field

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 39
51200 Kuala Lumpur

UAT URL
HTML Format: https://staging-gateway.revpay.com.my/enrolment

JSON Format: https://staging-gateway.revpay.com.my/enrol_json

Production URL
HTML Format: https://gateway.revpay.com.my/enrolment

JSON Format: https://gateway.revpay.com.my/enrol_json

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 40
51200 Kuala Lumpur

2.16 Customer Card Enrolment Request Parameters (Merchant to revPAY) -
JSON

Merchant send customer card enrolment request parameters to revPAY Payment Gateway via JSON format.

Request

URL : {BaseURL}/enrol_json

Method : HTTPS POST

Request Body :

{
"Revpay_Merchant_ID" : "MER00000000001",
"Reference_Number" : "RF201774111",
"Amount" : 4.00,
"Currency" : "MYR",
"Device_ID" : "13154161261AJVGA",
"Customer_ID" : "110034876666",
"Customer_Name" : "ChangBS",
"Customer_Email" : "[email protected]",
"Customer_Contact" : "0166164216",
"Geo_Location" : "(3.192391, 101.659432)",
"Card_Type" : "02",
"Card_Holder_Name" : "Chang Boon Sun",
"Funding_Pan" : "4430556100883166",
"Funding_Exp_Date" : "202012",
"Funding_CVV" : "123",
"Card_Issuer_Bank_Country_Code" : "MY",
"Key_Index" : 1,
"Signature" :
"0716dc1863519f53d47a11ec603d402782222083b2178f596d210fcb93287e81412dd529fa2adddd8e0cdfa2ddf0
bb5e8421f55a105196d4ee58961b253b98a1",
"Return_URL" : "https://domain.com/return_url",
"Backend_URL" : "https://domain.com/backend_url"
}

REVENUE GROUP OF COMPANIES Title: revPAY Merchant API

Wisma Revenue Date: 16 Jul 2021 Version: 1.41
No 12, Jalan Udang Harimau 2,
Kepong Business Park, Page 41
51200 Kuala Lumpur

2.17 Customer Card Enrolment Response Parameters (revPAY to Merchant) -
Fronted

Merchants will receive the HTTPS POST/JSON response from revPAY after the payment is completed.
revPAY will use the values in the parameter “Return_URL” which is provided by the Merchant during the payment
request, as a location to return these payment results to. revPAY will respond these transaction results to
merchant’s “Return_URL” through the redirect method (Browser to Browser).

Every payment response message will include a Signature value for indefinite message content to be valid.
Merchant is strongly recommended to generate a Signature value based on the format given in Section 3.1
Signature of Response for matching purposes.

No Field Name Data Type (Size) M/O Description

1 Revpay_Merchant_ID Alpha-numeric (50) M Unique merchant account number as

assigned by revPAY.

2 Transaction_ID Alpha-numeric (50) M Payment Transaction ID generated by

revPAY.

3 Reference_Number Alpha-numeric (50) M Merchant Reference Number of the order

that uniquely identifies the transaction in

the merchant’s system.

4 Amount Numeric (12) M Payment amount.

5 Currency Alphabet (3) M Payment currency code.

6 Card_Type Alpha-numeric (3) M Customer’s card type. (See Appendix H)

7 Card_Category Alpha-numeric (3) M Customer’s card category. (See Appendix I)

8 Card_Provider_Type Alpha-numeric (30) M Customer’s card type provider.

9 Funding_Pan_Mask Alpha-numeric (20) M Customer’s card account number with

masking. System will share the number with

first 6 and last 4 digits in clear, the rests are

marked with “*”. E.g: 484281******7590

10 Funding_Bin Numeric (6) M Customer’s card bin.

11 Funding_Exp_Date Numeric (6) M Customer’s card expiration year and month.

Format: YYYYMM

12 Card_Brand Alpha-numeric (30) M Customer’s card brand. (See Appendix J)

13 Card_Issuer_Bank_Name Alpha-numeric (50) O Customer’s card issuing bank name.

14 Card_Issuer_Bank_Count Alpha (3) M Issuer bank’s country code. Following ISO

ry_Code 3166-3 country codes.

15 Card_Issuer_Bank_Count Alpha-numeric (2) M Issuer bank’s country code. Following ISO

ry_Desc 3166-2 country codes.

16 Token_Pan Alpha-numeric (50) M Customer’s card tokenization reference

number.

17 Token_Exp_Date Numeric (6) M Customer’s card tokenization account

expiration year and month. Format:

YYYYMM

18 Response_Code Alpha-numeric (6) M Payment status code. (See Appendix C)

19 Error_Description Alpha-numeric (100) O Payment status description.

20 Key_Index Integer (3) M The index of key provided by revPAY to

encrypt the signature. (See Appendix D)

21 Signature Alpha-numeric (128) M SHA512 checksum signature. (See Electronic


Signature)

22 Request_Datetime Datetime M Payment request datetime.