What is the feature?
GoDaddy Tap to Pay would allow merchants to effortlessly process customer payments directly through the GoDaddy App.
‍
Who is this feature for?
Entrepreneurs and small business owners who rely on the GoDaddy app for managing their sales and operations. This feature empowers them to accept payments seamlessly through the app, enhancing their ability to conduct business efficiently while on the move.

Where is this feature going to be launched?
This new feature was launched to be used in GoDaddy Android phones.

Why would this help?
This feature would allow GoDaddy merchants to process payments directly on their phones, transforming them into a mobile Point of Sale (PoS) system. By eliminating the need for traditional PoS hardware like card readers, merchants can conduct transactions anywhere, enhancing convenience and flexibility.

Where would this feature live?
In the GoDaddy Android App.

How would Tap to Pay work?
The Tap to Pay feature operates by utilizing Near Field Communication (NFC) technology, allowing seamless transactions similar to other digital payment methods.

Why build this?

The introduction of Tap to Pay for GoDaddy Android aims to:
• Expand the app's capabilities.
• To offer Android users the same seamless payment experience that iPhone users enjoy.
• Boost app engagement and attract more users to the platform.

In the flow where a customer is browsing a merchant's store in person, here's how it would play out in the real world:

Please note that the case study below has only been shown in part to comply with the company's NDA policy.

There are two personas in the App flow: The GoDaddy Merchant and the Customer.

Understanding NFC and Tap to Pay in iPhone

NFC technology enables contactless payments by allowing devices to communicate when they are in close proximity. In iPhones, the NFC reader is strategically placed at the top of the device to facilitate easy tap-to-pay transactions.

‍
In the image below, the red rectangle displays where the NFC reader is located on an iPhone.

Android phones are built a little different though. Here's what we found:

The NFC sensor is generally on the back of the phone, either in the center, lower or upper portions.

‍
Confusing for the users right? Which area of the phone would they have to tap to pay?

We thoroughly reviewed the Android documentation to pinpoint the location of NFC readers. Interestingly, each Android manufacturer provides specific details for their models.

We also skimmed through what models our Android users were using the GoDaddy App on to get an idea of where the NFC reader could be located.
After cross-referencing this with other documentation on the internet we came to the conclusion:

Most Android users would have the NFC reader on the back of their phone, meaning they'd have to tap the back of their phone to pay.

Our game plan:

1) Have a campaign or demo to show how Android users how to use the Tap to Pay feature when they open the app.
2) Have a test flow where merchants can test the feature before using it for an actual payment.
3) Make the actual tap to pay flow visually rich to inform users on how to use the Tap to Pay feature.

Questions we had:
1) Would the demo work? What if a user skips it?
2) Would a test flow be an overkill? Would it be a waste of engineering effort?
3) Would users understand where exactly to tap to pay if they went straight to the flow?

We had all these questions - where would we get answers?
Testing with our customers.

When it came to designing the mocks - I used Material design guidelines and also the existing Android App as a base.

Here's the flow in action: