Sankalp Shakti Demo
hcvdshcvdhscvghds
hcvdshcvdhscvghds
- No tags were found...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Step 5: Sage Pay redirects your customer to their Issuer<br />
The customer’s browser<br />
is redirect to their Card<br />
Issuing Bank’s 3D-<br />
Secure authentication<br />
pages. These vary from<br />
bank to bank, but their<br />
purpose is to require the<br />
customer to<br />
authenticate themselves<br />
as the valid cardholder.<br />
3D-Secure is much like<br />
an online version of<br />
Chip and Pin. The<br />
customer may be asked<br />
to answer questions at<br />
their card issuer’s site<br />
(these might be a<br />
simple password,<br />
characters from a password, or numbers generated via card devices, depending on the level of<br />
security employed by the bank) and in so doing, the bank is validating the customer’s right to use the<br />
card for the transaction on your site. However, some issuers will automatically authenticate what they<br />
consider low risk transactions and not ask any questions.<br />
If they determine that the<br />
person attempting the<br />
transaction is the actual<br />
cardholder, they assume<br />
liability for the fraudulent<br />
use of that card during<br />
this transaction and you<br />
are protected from what<br />
are known as<br />
‘Chargebacks’.<br />
Chargebacks occur<br />
when the cardholder<br />
subsequently challenges<br />
an authorisation with<br />
their issuing bank on the<br />
premise that it was<br />
obtain fraudulently. For<br />
more information on chargebacks and the rules around liability shift, please contact your acquiring<br />
bank.<br />
This level of protection for you is only afforded by 3D-Secure, which is why we recommend you enable<br />
this on your Sage Pay account. You can enable and specify rules for 3D-Secure in MySagePay.<br />
Sage Pay Form Integration and Protocol and Guidelines 3.00 Page 14 of 61