You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the beta but functional MOLPay React Native payment module that is ready to be implemented into any React Native project npm install module. An example application project
10
-
(MOLPayReactExampleProject) is provided for MOLPayXDK framework integration reference.
9
+
This is the beta but functional Razer Merchant Services React Native payment module that is ready to be implemented into any React Native project npm install module. An example application project
10
+
(MOLPayReactExampleProject) is provided for Razer Merchant Services XDK framework integration reference.
11
11
12
12
## Recommended configurations
13
13
@@ -126,7 +126,7 @@ Parameter and meaning:
126
126
"paydate" - The transaction date
127
127
"order_id" - The transaction order id
128
128
"channel" - The transaction channel description
129
-
"txn_ID" - The transaction id generated by MOLPay
129
+
"txn_ID" - The transaction id generated by Razer Merchant Services
130
130
131
131
* Notes: You may ignore other parameters and values not stated above
132
132
@@ -138,10 +138,10 @@ Parameter and meaning:
138
138
139
139
Parameter and meaning:
140
140
141
-
"Communication Error" - Error starting a payment process due to several possible reasons, please contact MOLPay support should the error persists.
141
+
"Communication Error" - Error starting a payment process due to several possible reasons, please contact Razer Merchant Services support should the error persists.
142
142
1) Internet not available
143
143
2) API credentials (username, password, merchant id, verify key)
144
-
3) MOLPay server offline.
144
+
3) Razer Merchant Services server offline.
145
145
```
146
146
147
147
## Prepare the Payment detail object
@@ -151,7 +151,7 @@ var paymentDetails = {
151
151
// Optional, REQUIRED when use online Sandbox environment and account credentials.
152
152
'mp_dev_mode': false,
153
153
154
-
// Mandatory String. Values obtained from MOLPay.
154
+
// Mandatory String. Values obtained from Razer Merchant Services.
155
155
'mp_username' : 'username',
156
156
'mp_password' : 'password',
157
157
'mp_merchant_ID' : 'merchantid',
@@ -210,7 +210,7 @@ var paymentDetails = {
210
210
// Optional, credit card transaction type, set "AUTH" to authorize the transaction.
211
211
'mp_tcctype': '',
212
212
213
-
// Optional, required valid credit card channel, set true to process this transaction through the recurring api, please refer the MOLPay Recurring API pdf.
213
+
// Optional, required valid credit card channel, set true to process this transaction through the recurring api, please refer the Razer Merchant Services Recurring API pdf.
214
214
'mp_is_recurring': false,
215
215
216
216
// Optional, show nominated channels.
@@ -255,10 +255,10 @@ var paymentDetails = {
255
255
## Start the payment module
256
256
257
257
```
258
-
//import molpay package
258
+
//import Razer Merchant Services package
259
259
var molpay = require("molpay-mobile-xdk-reactnative-beta");
@@ -282,11 +282,11 @@ Navigate to `node_modules/molpay-mobile-xdk-reactnative-beta/android/src/main/ja
282
282
283
283
1) The user initiate a cash payment, upon completed, the XDK will pause at the “Payment instruction” screen, the results would return a pending status.
284
284
285
-
2) The user can then click on “Close” to exit the MOLPay XDK aka the payment screen.
285
+
2) The user can then click on “Close” to exit the Razer Merchant Services XDK aka the payment screen.
286
286
287
287
3) When later in time, the user would arrive at say 7-Eleven to make the payment, the host app then can call the XDK again to display the “Payment Instruction” again, then it has to pass in all the payment details like it will for the standard payment process, only this time, the host app will have to also pass in an extra value in the payment details, it’s the “mp_transaction_id”, the value has to be the same transaction returned in the results from the XDK earlier during the completion of the transaction. If the transaction id provided is accurate, the XDK will instead show the “Payment Instruction" in place of the standard payment screen.
288
288
289
-
4) After the user done the paying at the 7-Eleven counter, they can close and exit MOLPay XDK by clicking the “Close” button again.
289
+
4) After the user done the paying at the 7-Eleven counter, they can close and exit Razer Merchant Services XDK by clicking the “Close” button again.
290
290
291
291
## XDK built-in checksum validator caveats
292
292
@@ -298,12 +298,12 @@ Navigate to `node_modules/molpay-mobile-xdk-reactnative-beta/android/src/main/ja
298
298
299
299
## Support
300
300
301
-
Submit issue to this repository or email to our support@molpay.com
301
+
Submit issue to this repository or email to our support-sa@razer.com
302
302
303
-
Merchant Technical Support / Customer Care : support@molpay.com<br>
304
-
Sales/Reseller Enquiry : sales@molpay.com<br>
305
-
Marketing Campaign : marketing@molpay.com<br>
306
-
Channel/Partner Enquiry : channel@molpay.com<br>
307
-
Media Contact : media@molpay.com<br>
308
-
R&D and Tech-related Suggestion : technical@molpay.com<br>
309
-
Abuse Reporting : abuse@molpay.com
303
+
Merchant Technical Support / Customer Care : support-sa@razer.com<br>
0 commit comments