1. What are the key components of Maybankard.net?
  2. In what currency does Maybank e-commerce credit card facility settle payments received by merchants?
  3. What are the charges for Maybank e-commerce credit card facility payment acceptance services?
  4. Do I have to install a shopping cart in my web site?
  5. Do I need to have a web site before I can apply for your services?
  6. I am running online operations outside Malaysia. May I join?
  7. My company operates more than one e-commerce site. Do I have to apply for multiple merchant accounts?
  8. What is 3D SSL?
  9. What is a chargeback?
  10. How does 'Verified by Visa' or 'MasterCard SecureCode' work?
  11. I already use SSL; why is 'Verified by Visa' or 'MasterCard SecureCode' better?
  12. What's involved in implementing 'Verified by Visa' or 'MasterCard SecureCode' and how long will it take?
  13. How will cardholders know that I have 'Verified by Visa' or 'MasterCard SecureCode'?
  14. Once it is installed, what do I have to do?
  15. How much maintenance is required for the Merchant Plug-In?
  16. How much longer does a 'Verified by Visa' or 'MasterCard SecureCode' transaction take?
  17. How do I recognise a 'Verified by Visa' or 'MasterCard SecureCode' registered card?
  18. How do I treat cards that are not registered for 'Verified by Visa' or 'MasterCard SecureCode'?

1. What are the key components of Maybankard.net?
We offer a payment acceptance solution to process MYR and USD currency transactions. Apart from a comprehensive range of user administration tools, reverse and refund, and transaction reporting, we provide value-added processing and security features of 3D security protection.

Back to top

2. In what currency does Maybank e-commerce credit card facility settle payments received by merchants?
Currently we accept payments in MYR and USD currencies. Holders of overseas credit cards who shop at the site can settle transactions in USD. The issuing banks of such credit cards convert the payments into their respective currencies and charge the cardholders with such amounts. However, settlement to merchants by Maybank will be in Malaysian Ringgit (MYR).

Back to top

3. What are the charges for Maybank e-commerce credit card facility payment acceptance services?
Merchants will need to pay a one-off set up charge, an annual service charge for Maybankard.net and transaction commissions based on the payments received.

Back to top

4. Do I have to install a shopping cart in my web site?
We strongly recommend that you do. To operate e-commerce activities, web sites should have online catalogues that front their payment facilities which are known as shopping carts. Our payment services require the installation of a shopping cart on the merchant's site. You will need to liaise with any IT vendor or Internet Service Provider that provides the shopping cart facilities software.

Back to top

5. Do I need to have a web site before I can apply for your services?
Yes, in order to implement the service, a merchant has to own and run a web site. However, at the time application, you don't need to have a running web site. You may contact us when the site is ready for publishing, or you may apply while your site is being developed.

Back to top

6. I am running online operations outside Malaysia. May I join?
Currently we provide payment acceptance services to all businesses, organisations and charitable bodies registered in Malaysia only.

Back to top

7. My company operates more than one e-commerce site. Do I have to apply for multiple merchant accounts?
Yes, our merchant ID is offered for use at only ONE web site. Merchants should apply for separate IDs for each of the sites they operate.

Back to top

8. What is 3D SSL?
3D SSL is the new security requirement for online purchases based on new technology implemented by Visa known as 'Verified by Visa', and by MasterCard known as 'MasterCard SecureCode'. They are designed to provide online retailers the added security of having issuing banks authenticate their individual cardholders and qualify their online transactions for protection against "cardholder unauthorised" or "I didn't do it" chargeback. The objective is to ensure that only the cardholder can make online purchases via the Internet using his/her credit card.

Back to top

9. What is a chargeback?
A chargeback is the forced reversal of a transaction by the credit card issuing bank. A chargeback takes place when notification is received from the cardholder's issuing bank stating that it has received a dispute notice from the cardholder, whose card had been charged by our merchants. In certain cases defence is possible (e.g. order denial while delivery is completed in deed) — given that merchants are able to provide adequate evidence. Sometimes (for example, fraudulent card usage) a chargeback is made immediately. Please note that excessive chargeback may result in the revision of service terms, service suspension or even termination.

Back to top

10. How does 'Verified by Visa' or 'MasterCard SecureCode' work?

When a cardholder is on your checkout page, the 'Verified by Visa' or 'MasterCard SecureCode' service performs the following to ensure that the cardholder is authorised to make this transaction:

  • It initiates a pop-up box into which the cardholder enters a private code that is registered with the credit card issuing bank.
  • It passes the authentication value in your normal authorisation request procedures and, if approved, receives an authorisation that binds that customer to that transaction. This authentication value is transported using a Visa ECI and MasterCard UCAF data field.


Back to top

11. I already use SSL; why is 'Verified by Visa' or 'MasterCard SecureCode' better?
'Verified by Visa' or 'MasterCard SecureCode' also uses SSL, but adds the important security function of confirming the identity of the Visa or MasterCard cardholder, creating a virtual "card present" environment. It is this important additional function that enables Card Issuers to provide your business with guaranteed payment.

Back to top

12. What's involved in implementing 'Verified by Visa' or 'MasterCard SecureCode' and how long will it take?
You will need to integrate a Merchant Plug-In with your existing server, or your IT service provider may be able to do this on your behalf. There are no required changes to the customer-facing portion of your e-commerce application. On average, the whole process takes 3-5 man days. Maybank may provide assistance with this process.

Back to top

13. How will cardholders know that I have 'Verified by Visa' or 'MasterCard SecureCode'?
A 'Verified by Visa' and 'MasterCard SecureCode' logo or participation mark must be featured on your web site.

Back to top

14. Once it is installed, what do I have to do?
Nothing. The Merchant Plug-In automates the process with the Card Issuers.

Back to top

15. How much maintenance is required for the Merchant Plug-In?
Like any software, the Merchant Plug-In may experience problems that require troubleshooting, and upgrades may be available from time to time. Maybank will provide the guide for these circumstances.

Back to top

16. How much longer does a 'Verified by Visa' or 'MasterCard SecureCode' transaction take?
On average, the 'Verified by Visa' or 'MasterCard SecureCode' process adds 10-20 seconds to the total transaction time.

Back to top

17. How do I recognise a 'Verified by Visa' or 'MasterCard SecureCode' registered card?
The Merchant Plug-In automates this process for you by checking with the Card Issuer to see if the card is registered and then automating the process for authentication.

Back to top

18. How do I treat cards that are not registered for 'Verified by Visa' or 'MasterCard SecureCode'?
Process card transactions that don't have 'Verified by Visa' or 'MasterCard SecureCode' with the same precautions that you currently use, understanding that these transactions do not carry the same benefits of guaranteed payment as a 'Verified by Visa' or 'MasterCard SecureCode' transaction.

Back to top