Location_id not being respected in the checkout api - continued

Questions
1

For some reason - the forum not let me post to the existing thread for a few days. I am still hoping to resolve this problem :man_shrugging:t2:

existing thread is here

@Bryan-Square it is still a problem :man_shrugging:t2: Am I not allowed to post screenshots ?

2

@Bryan-Square Here is example that illustrates the problem :

When I create a checkout link with "location_id": "LKEJS0WJG0NSP",
which location name should appear at the top of the link page ?
here are the 2 options:

  • screenshot1 removed -
  • screenshot2 removed -

Here are details of the link created:

  {
    "payment_link": {
      "id": "O7CQW5HLOFS7M5FO",
      "version": 1,
      "order_id": "blbWeDp73daFLIyktOZGqxUkLILZY",
      "url": "https://square.link/u/F1ybFsex",
      "created_at": "2022-10-08T03:29:09Z"
    },
    "related_resources": {
      "orders": [
        {
          "id": "blbWeDp73daFLIyktOZGqxUkLILZY",
          "location_id": "LKEJS0WJG0NSP",
          "source": {
            "name": "2022test"
          },

Please follow the link becasue it shows the wrong name at the top of the page.

3

When I click on that link the location_id is correct in the URL. Are you referring to the name of the location on the top of the page? :slightly_smiling_face:

4

yes the name in the middle at the top of the page - as I have written many times - including in the original post.

5

Screenshot 2022-10-08 135531
Screenshot 2022-10-08 135531712×296 24 KB

This is one - note the location_id and the location business name

6

this is the other location - again note the location_id and the business name

Screenshot 2022-10-08 135646
Screenshot 2022-10-08 135646725×295 22 KB

7

The team is aware that the business name that’s listed in the Dashboard for the location isn’t correctly showing the business name in the payment link and are working on a fix. :slightly_smiling_face:

1 Like
8

@Bryan-Square Thank you :pray:t2::pray:t2:

9

Hi @Bryan-Square :blush:
Is there any update yet from the team ?
specifically about when this problem is likely to be fixed…

10

The team has deployed a fix and this should be working as expected now. :slightly_smiling_face: