بطاقة الولاء اللي تطلع لما تقرب من محلك: كيف يشتغل الموقع داخل Apple Wallet وGoogle Wallet وكيف تضبطه صحThe Loyalty Card That Shows Up When You Are Near the Shop: How Location Works in Apple Wallet and Google Wallet and How to Set It Up Right

Key terms

Pass

A small file the customer saves in Apple Wallet or Google Wallet, with the shop name, points or stamps and a barcode.

locations (Apple Wallet)

A list inside the pass itself with up to ten places. Each has a latitude, a longitude and an optional short line for the Lock Screen.

merchantLocations (Google Wallet)

The shop locations you add to a Google Wallet pass, up to ten per class and ten per object.

relevantText

The line you write that shows with the pass on the iPhone Lock Screen, such as "Our branch is steps away".

The steps

1. 1

   Step 1

   Get the idea before you set anything

   The shop does not send you anything when you walk past. It writes its location into the pass, and the phone and Wallet decide when the pass is useful.

   On iPhone, Apple describes this as passive: the pass appears on the Lock Screen, with no alert and no sound.

   On Android, Google Wallet posts a sticky Lock Screen notification that goes away when you leave the area.

   Tip: Do not promise customers a buzzing alert on iPhone. What happens is the pass shows on the Lock Screen.

2. 2

   Step 2

   Add your branches to the Apple Wallet pass

   In pass.json add the locations key. Each entry has latitude and longitude, plus optional altitude and relevantText.

   The limit is ten locations per pass. With more branches, Apple says start with the best ones and update the pass to change the list.

   Store cards use a small radius. Apple's older Wallet guide puts that on the order of a hundred meters or closer, and says the exact radius is an implementation detail that may change.

   PromptPrompt to draft the locations list

   Copy

   My shop is [shop name] with these branches: [branch name, address, coordinates if I have them]. Draft the locations array for an Apple Wallet pass.json, at most ten entries ordered by importance, each with a short helpful relevantText saying why the pass is useful here. Do not add any discount or number I did not give you.

3. 3

   Step 3

   Use maxDistance only to make the area smaller

   maxDistance is in meters, and the system uses the smaller of your value and its default distance.

   So it can only shrink the area, never grow it. Useful when your branch sits inside a mall and you do not want the pass showing in the car park.

   Tip: Apple asks you not to add inaccurate locations to make the pass show up more.

4. 4

   Step 4

   Write a relevantText that helps

   This line is what the customer reads on the Lock Screen. Apple's own example is "Store nearby on 1st and Main".

   Keep it short and say why the pass is showing now: the branch is close, or the next stamp completes a reward. Any offer you write must be real.

   PromptPrompt for Lock Screen lines

   Copy

   Write five short relevantText lines for a [type of shop] loyalty pass in [area]. Each under 40 characters, telling the customer the branch is close or reminding them of their stamps. No discount or number that is not in this list: [my real offers].

5. 5

   Step 5

   Add the locations in Google Wallet

   In Google Wallet use merchantLocations on the class or the object, up to ten on each, set with insert, patch or update.

   Two differences: Google decides how close the user must be and how long they stay before the notification, and Google writes the notification text, not you.

   It only reaches users who turned on notifications and gave the Google Wallet app precise, always on location access.

   developers.google.com

   

6. 6

   Step 6

   Test on a real device

   Apple notes that Simulator does not show passes on the Lock Screen, so test on a real iPhone standing at the branch.

   On Android, test with an account that gave Wallet always on location access, because without it no notification arrives.

Ready prompts to copy

Here is my loyalty pass.json: [paste the file]. Tell me how many entries are in locations, whether each has a valid latitude and longitude, whether relevantText is short and clear, and whether maxDistance is set and to what. Do not add any field you do not know exists in Apple's documentation.