You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We intend to use SumUp as a payment gateway, where clients can pay for services inside our own app. Previously it wasn't possible to use iOS SDK because it was intended to be used with terminals, but after introduction of the Tap to Pay feature we consider this as a good option for our clients to self-serve using their own iPhones.
I realize that there is no functionality to store and reuse the card, so that client will need to pull out his physical card and put it near phone on each transaction, but since we expect big transactions - this additional physical action of tapping the phone can be perceived as a security measure and may be considered as plus by our clients.
However, while adding the SDK, I've realized that during activation of Tap to Pay there are introductory screens, which are targeted specifically to merchants (see screenshots below). Our clients are going to be confused by the graphics and verbal messages shown on these screens.
Is there a way to either skip the introductory screens or replace their content with a content of our own, which would be more appropriate for our business?
For the time-being the only fallback strategy of us is to see if we can use Payment Widget or Swift Checkout inside a WebView or implement a custom UI for user to enter card details (reinvent the wheel). But any of these are workarounds because the iOS SDK would be more appropriate to be used in a native iOS app.
The text was updated successfully, but these errors were encountered:
Hello,
We intend to use SumUp as a payment gateway, where clients can pay for services inside our own app. Previously it wasn't possible to use iOS SDK because it was intended to be used with terminals, but after introduction of the Tap to Pay feature we consider this as a good option for our clients to self-serve using their own iPhones.
I realize that there is no functionality to store and reuse the card, so that client will need to pull out his physical card and put it near phone on each transaction, but since we expect big transactions - this additional physical action of tapping the phone can be perceived as a security measure and may be considered as plus by our clients.
However, while adding the SDK, I've realized that during activation of Tap to Pay there are introductory screens, which are targeted specifically to merchants (see screenshots below). Our clients are going to be confused by the graphics and verbal messages shown on these screens.
Is there a way to either skip the introductory screens or replace their content with a content of our own, which would be more appropriate for our business?
For the time-being the only fallback strategy of us is to see if we can use Payment Widget or Swift Checkout inside a WebView or implement a custom UI for user to enter card details (reinvent the wheel). But any of these are workarounds because the iOS SDK would be more appropriate to be used in a native iOS app.
The text was updated successfully, but these errors were encountered: