Mobile and In-app payments
Technical and Administrative questions related to Peach.AppPay Product
WebHooks are a way to get device-independent notifications to your server whenever a transaction is processed through the iOS or Android apps.
While the ...
Wed, 24 Aug, 2022 at 1:27 PM
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
Peach Payments supports mobile interfaces in 2 ways: Hosted front end: In this option Peach Payments provides you a mobile optimised payment frontend whic...
Tue, 14 Feb, 2023 at 10:52 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...
Sat, 30 Apr, 2022 at 3:38 PM
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...
Tue, 29 Nov, 2022 at 1:52 PM
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