Frequently Asked Questions

Frequently Asked Questions

Frequently Asked Questions

Q: When calling the adjust charge, capture, refund charge and get transactional data endpoints, will the authentication be the same as it is for the catalog upload endpoint?

A yes, it is the same AWS IAM based auth

Q: Will there be an indicator in the order/purchases request that it is a card present transaction and JWO is doing the charging?

A: If the authEvents payloadType is FINANCIAL then the entry is credit cart otherwise if the value is SCAN_CODE then the entry type is app entry.

{
    "authEvents": [
        {
            "id": "string",
            "timestamp": "2025-05-02T00:05:18Z",
            "location": "ENTRY",
            "payloadType": "FINANCIAL",
            "scanResult": {
                "id": "string",
                "type": "SHOPPER"
            }
        }
    ]
}

Q: Will card data such as the card type and last 4 be sent in the order/purchases request for card present transactions? We will need this data to tie it together with the shopping trip id for the transactional data request

A: No, you will need to tie the data together in your solution. When the cart is delivered to you and you calculate the charge then you will call the payment service and record the payment for the cart which will include this data.

Q: For delegated orders, when Just Walkout sends cart to /order/purchases endpoint at 3P connector, what would we send in the shoppingTrip.authEvents.scanResult.id value? Is anything base64 encoded?

A: Amazon sends the customer a loyalty scan to the customer in /v1/identity/scan
the payload scanEvent.id will have a base64 encoded value for the scanned QR in the store. The customer is expected to decode that id and resolve it and return an id back to us.

Example of an incoming to customer endpoint:

{
    "requestId": "string",
    "storeId": "string",
    "scanEvent": {
        "id": "MTExMS0yMjIyLTMzMzMtNDQ0NC01NTU1LTY2NjY= ",
        "timestamp": "2024-04-25T13:03:14Z",
        "location": "ENTRY",
        "value": "string",
        "channel": "OPTICAL"
    }
}

Customer for example will decode that string “MTExMS0yMjIyLTMzMzMtNDQ0NC01NTU1LTY2NjY=” and do their operation against the id then return a response with an id like this for example

{
  "id": "1111-2222-3333-4444-5555-6666",
  "type": "SHOPPER",
  "action": "ACCEPT"
}

When we send the cart to the customer ,they should expect 1111-2222-3333-4444-5555-6666 in the cart payload in authEvents.scanResult.id

{
  "authEvents": [
    {
      "id": "string",
      "timestamp": "2025-05-02T00:05:18Z",
      "location": "ENTRY",
      "payloadType": "FINANCIAL",
      "scanResult": {
        "id": "1111-2222-3333-4444-5555-6666",
        "type": "SHOPPER"
      }
    }
  ]
}

Q: What should my AWS IAM policy look like to allow invoking JWO APIs?

A: This is a sample policy and you should follow your company best practices, you can get the value for the AWS resource ARN by working with the Amazon team

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PaymentsAPIAccess",
            "Effect": "Allow",
            "Action": "execute-api:Invoke",
            "Resource": "<AMAZON_RESOUCE_ARN>"
        }
    ]
}

Q: What should I do if any of the items in the cart cannot be recognized in my catalog? A: Amazon Just Walk Out expects a successful response when an API payload contains the required fields as specified in the developer documentation.

While validating the payload, you should focus only on verifying the presence and format of the required fields - do not reject carts based on content validation errors (such as mismatched cart items).

If you need implementation examples, refer to sample code here