New PSP/ISO service: With COPYandPAY, PAY.ON simplifies payment integration for merchants

By Christopher Taine on 21. February 2013 in Inside PAY.ON, Open Payment Technology
0
0

PAY.ON reduces the payment integration time for online shops and SaaS providers to just a few minutes with its new service COPYandPAY. Easy, easier, easiest: COPYandPAY simplifies complex payment integration when using APIs and makes the laborious task of adapting payment processes to one’s own design via iFrames a thing of the past. With COPYandPAY merchants can host their payment solution themselves and still be PCI-compliant. To customise the payment process, a library of ready-made widgets is available, which can be adapted to the merchant’s own specifications in a fully flexible manner. In terms of technology, the new ‘COPYandPAY’ service is based on the platform-as-a-service solution PaySourcing.

 

COPYandPAY also offers complete freedom when it comes to selecting payment methods: over 100 payment methods such as Visa, MasterCard, Amex, SOFORT Überweisung and PayPal and more than 250 connections to financial service providers. With this method of integration, 3D Secure (Verified by Visa and MasterCard SecureCode) is also immediately available. Furthermore, because it is based on HTML 5, COPYandPAY is directly compatible with smartphones and tablets.

 

 

Markus Rinderer, CEO of PAY.ON AG: COPYandPAY is opening up a new customer segment for payment service providers/independent sales organizations: online shops that are looking for an easier integration of payment options, are cost-oriented but don’t want to forego applicable standards. For online shops, COPYandPAY is the most effective key to more sales, as it currently offers the simplest integration of all familiar payment methods.’

 

Christopher Taine

About the Author

Christopher TaineView all posts by Christopher Taine
Social Media & PR Manager Spreading the word about PAY.ON's products and services.

0 Comments

Add comment

Leave a Reply

Your email address will not be published. Required fields are marked *

*