Sankalp Shakti Demo

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