Who are WorldPay?
WorldPay specialises
is handling secure online transactions.
They are part of The Royal Bank of
Scotland Group, the 5th biggest banking
group in the world.
For
millions of people around the world,
WorldPay is the way to pay - trusted
and secure.
WorldPay enables their
customer (companies like Nails and
Things) to accept payments over the
internet, by phone, fax and mail using
WorldPay's secure payment services.
They accept Visa,
MasterCard, Diners, American Express,
JCB and all the major credit cards.
Not forgetting debit cards and local
payment schemes like Switch, Laser,
Electron and more.
The
following extract was taken from
the WorldPay website (view
it here)
Shopper Transaction
Security
Security is probably one of the most
significant concerns for both the shopper
and the retailer during an online transaction.
In reality an online transaction is
probably more secure than a card transaction
in a shop or conducted over the telephone
or by fax, as the information transmitted
online is highly encrypted using complicated
logarithm combinations.
The WorldPay payment system uses a
combination of both established and
innovative techniques to ensure the
security and integrity of all sensitive
data. Furthermore, our public web servers
are certified by Thawte, a public Certificate
Authority, ensuring that both the shopper
and retailer can have confidence that
nobody can impersonate WorldPay to
obtain confidential information.
Transaction Encryption
The transfer of the purchase details
from the retailers site to WorldPay
are encapsulated using our own encrypted
and digitally-signed protocol. This
uses a combination of standard methods
such as PGP, RSA and MD5 to ensure
that the information passed is secure
and tamper-proof.
Data Storage
Data storage on WorldPay systems, and
the communication between WorldPay
and the worldwide banking networks,
is regularly audited by the banking
authorities to ensure a secure transaction
environment. We also ensure that
we stay up-to-date with the latest
versions of any third-party code
we use, and continually review our
own proprietary code.
The above details
were accurate at the time of initial
publication. Details may have since
changed. |