Mobile and In-app payments
Technical and Administrative questions related to Peach.AppPay Product
The unique identifier for a transaction which also match the UniqueID in our merchant console (BIP) is the processorIdentifier.
We have two additional id...
Sat, 21 Dec, 2019 at 7:13 AM
Yes, Peach Payments supports mobile interfaces in 2 ways:
Hosted front end: In this option Peach Payments provides you a mobile optimized payment fro...
Sat, 21 Dec, 2019 at 7:13 AM
As per the current PASA rules (which are subject to change), transactions originating and completed on mobile phones do not require 3DSecure authentication....
Sat, 21 Dec, 2019 at 7:13 AM
After careful consideration, PASA has made a decision to exclude ecommerce transactions that are concluded on a mobile device (i.e. mobi site or native appl...
Sat, 21 Dec, 2019 at 7:13 AM
Yes, a token that has been created with our SDK can be used in eCommerce as well.
To reuse the token do the following:
Create a token with mobile.c...
Sat, 21 Dec, 2019 at 7:14 AM
The Peach SDK is accessing mobile.connect-resources.bundle using
[[NSBundle mainBundle] pathForResource:@"mobile.connect-resources" ofType:@&qu...
Sat, 21 Dec, 2019 at 7:14 AM
Tokenization using the mobile SDK is as easy as following the steps in our documentation available here: https://peachpayments.docs.oppwa.com/tutorial...
Mon, 22 Feb, 2021 at 10:11 AM
On challenge you may face when working with Phone Gap and using the Copy and Pay widget is the redirect back to Response URL (you specify this in the <fo...
Sat, 21 Dec, 2019 at 7:14 AM
The notificationUrl acts as a fail-safe to ensure that your server always has the final transaction status in the situation where the client device loses co...
Sat, 21 Dec, 2019 at 7:14 AM
When integrating the SDK, a value for both the shopperResultUrl and the notificationUrl are required. shopperResultUrl The shopperresulturl is the locat...
Sat, 21 Dec, 2019 at 7:15 AM