Rambus Inc. has teamed up with eftpos, the Australian domestic debit network, to help support secure transactions with Apple Pay for users in Australia. Through integration with the Rambus Token Service Provider (TSP) technology, eftpos is able to support Apple Pay, the easy, secure and private way to pay.
By utilising tokenisation, this TSP technology replaces sensitive information with unique reference numbers and is more secure than traditional plastic cards.
“With millions of eftpos-only debit cards distributed across Australia by its members, eftpos is the country’s most popular debit payment method,” said Chakib Bouda, CTO of the Rambus Payments Division. “This partnership allows more than a million consumers to enjoy secure mobile payments using Apple Pay, leveraging our proven EMV tokenisation software for trusted transactions.”
The Rambus TSP technology replaces traditional primary account numbers (PAN) with unique identifiers called payment tokens. By integrating the Rambus tokenisation software, participating eftpos members can use eftpos debit cards with Apple Pay for increased protection.
“Our partnership with Rambus gives us the ability to accelerate our secure mobile payments strategy and support Apple Pay,” said eftpos Acting CEO, Paul Jennings. “We are excited to move from our traditional card based payment method into mobile, offering our members in Australia the opportunity to benefit from the convenience and security of Apple Pay.”
Security and privacy are at the core of Apple Pay. When customers use eftpos debit cards with Apple Pay, the actual card numbers are not stored on the device, nor on Apple servers. Instead, a unique Device Account Number is assigned, encrypted and securely stored in the Secure Element on your device. Each transaction is authorised with a one-time unique dynamic security code.
The Rambus TSP is a comprehensive software platform that offers different solutions within the tokenised payment infrastructure. For more information on Rambus mobile payment solutions, click here.
Comment on this article below or via Twitter: @IoTNow_OR @jcIoTnow
