Project

General

Profile

Actions

Wiki » History » Revision 28

« Previous | Revision 28/31 (diff) | Next »
chin-yeh, 10/04/2011 06:17 PM


Wiki

The wiki for this project.

Merchant Account Details

Merchant Administration URL:

https://migs.mastercard.com.au/ma/login.s

use the lawsiew operator ID to login

Development:

Merchant ID: TEST001070001770
Operator ID: vpc_client
Access Code: D29BDF0E
Secure Hash Secret: DB0899F0D69B8B73D6CD3F53F4BF3420

2-Party VPC URL: https://migs.mastercard.com.au/vpcdps
3-Party VPC URL: https://migs.mastercard.com.au/vpcpay

Production:

Merchant ID: 001070001770
Operator ID: vpc_client
Access Code: DD8072CA
Secure Hash Secret: 274676AB08F4227C6AEA401FAB2DEAFF

2-Party VPC URL: https://migs.mastercard.com.au/vpcdps
3-Party VPC URL: https://migs.mastercard.com.au/vpcpay

Contact Person

MiGS:

Regional Technical Manager: Santoso, Herman [herman.santoso@merchant-solutions.biz]

eCosway:

Financial: Law, Siew Hong [SHLaw@cosway.com.my]
Developer: Hann, Chong Ting [cthann@cosway.com.my]
           Choo, Chin Yeh [cychoo@cosway.com.my]
           Kwan, Chooi Mey [cmkwan@cosway.com.my]

SCM

Integration in Dot Biz's Mall (CVS):

Host: cwyrnd2-server [IP address:192.168.2.11]
Path: d:/source/hongkong-mall
Tag: HEAD

Specification

See Specification

Frequently Asked Questions

Is there any test cards which could be used in test environment?

Card Type Card Number Expiry
MasterCard 51234567890123456 05/13
MasterCard 5313581000123430 05/13
VISA 4005550000000001 05/13
VISA 4557012345678902 05/13
AMEX 345678901234564 05/13
Bankcard(Australian Domestic) 5610901234567899 05/13
Diners 30123456789019 05/13

How to simulate Acquirer Response Code?

Available in TEST mode only.

Let's say, to simulate the response code 65, just submit a transaction with Amount of 8965, where 65 is the decimal value of the amount.

Any amount which is a multiple of 100 is an approved transaction, e.g. 100.

What does the response code XX means?

Refer to the document Virtual Payment Client Integration Reference in [MiGS] Integration Documents
  • Response Code (vpc_TxnResponseCode) - page 75
  • Acquirer Response Code (vpc_AcqResponseCode) - page 83
  • Error Codes(vpc_Message) - page 91

AMA - QueryDR

  • may return duplicate transaction if the order number is not unique
  • the database only contains data up to 3-day old.

How to enforce the CSC/CVV checking in the test environment?

[Important] The CSC response code has no bearing on the result of the payment in the development environment. However, in the production environment, MIGS allows you to adjust acceptance level from M to N.

Enter the following CSC/CVV code into the Security Code field:
  • 100 - (M) Valid or matched CSC
  • 101 - (S) Merchant indicates CSC not present on card (Visa Card only)
  • 102 - (P) CSC Not Processed
  • 103 - (U) Card issuer is not registered and/or certified
  • 104 - (N) Code invalid or not matched
  • 105 - (X) Code not processed (Master Card only)

Refer to the page 86, Virtual Payment Client Integration Reference in [MiGS] Integration Documents for more details.

List of possible Card Type Code

description of the card_type column in the interface table

2 character card type code

Updated by chin-yeh about 13 years ago · 28 revisions