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 iOS or Android apps. While the use...
Mon, 7 Aug, 2023 at 10:35 AM
The unique identifier for a transaction which also match the UniqueID in our merchant console (BIP) is the processorIdentifier. We have two additional i...
Tue, 20 Jun, 2023 at 1:54 PM
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
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...
Mon, 26 Jun, 2023 at 2:15 PM
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/tutorials/mobi...
Mon, 24 Jul, 2023 at 3:58 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...
Tue, 28 Nov, 2023 at 1:40 PM
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
Android permissions in Peach Payments mobile SDK More information on what permissions the Peach Payments android mobile SDK may require, depending on t...
Thu, 19 Oct, 2023 at 10:05 AM