Fraud Abuse Strategy Setup
Summary
The Fraud and Abuse strategy setup is a critical decision point that determines how risk assessment and gate entry decisions are managed in your Just Walk Out store. This process involves choosing how you want to handle shopper risk evaluation and payment mechanism validation.
Permission setup
Access to the Fraud and Abuse strategy is governed by the user permission in the merchant portal. The Fraud and Abuse strategy is automatically enabled for the stores have delegated payment processor. The logged in user also needs to have the Connector Configuration permission in the merchant portal
Step by step process
Step 1: Click on "Store Setup" tab on the homepage
Step 2: Select the relevant store
Step 3: After the page loads, a dropdown named "Store Entry" would be present, verify if fraud and abuse is present inside this list.
Step 4: If present, click on the next button on the bottom right of the page till we reach fraud and abuse section.
Step 5: Setting up your fraud and abuse strategy
| Strategy | Risk Model | Outstanding Balance | Responsibility |
|---|---|---|---|
| Amazon Managed | Input to Gate decision | Amazon Maintained | Amazon |
| Amazon Recommendation | Suggested input to gate decision | Amazon Maintained | Merchant/Amazon |
| Customer Managed | Merchant owned | Merchant Managed | Merchant |
Available strategy options depend on the specific Retail integration partnership with Amazon. The attached screenshot illustrates all possible strategies for a sample store.
For any additional questions, please consult with your Amazon team contact.
Note: If "Amazon Managed" is selected and saved as a strategy, the backend is updated and would not require connector setup. If the other strategies are selected, they would only be saved after the connector is setup.
Step 6: Setting up your Connector
The user will be required to provide two inputs for each endpoint to ensure successful communication between the Amazon systems and the company integration application. Endpoint (connector URL) and Endpoint Type (public or private API)
- Endpoint - A hostname for an API in API Gateway that is deployed to a specific Region.
- Endpoint Type - An API endpoint type refers to the hostname of the API. The API endpoint type can be edge-optimized, regional, or private. Depending on where the majority of the API traffic originates from. For more details on API types see AWS documentation.
Amazon Just Walkout services provide the ability to use Private or Public API endpoints. If you choose Edge-optimized or Regional AWS API GWs as the type of your end point, then you will need to select Public. Only Private AWS API Gateways need to be set as Private.
If this is your first time setting up the connector, you would be prompted to this page
If you already have set up a connector and want to edit your connector, click on the pencil icon beside the "Run Test" button
Step 7: Testing your connector
The user will be able to perform connectivity testing after completing the connector configuration. Connectivity testing ensures that the Amazon systems can communicate with the company systems. Further verification and testing is required before launching a store to ensure appropriate operations. For complete list of onboarding processes please coordinate with the Amazon team.
Connector API URL - Endpoint URL provided as an input for the connectors. A hostname for an API in API Gateway that is deployed to a specific Region.
Type - API endpoint type which was chosen by you during configuration.
Connectivity Details - This is the connector connectivity status with details about the previous api call. It can have below values:
-
Untested - The endpoint is saved recently and testing is not completed
-
Tested - This endpoint is tested and would have all the details of this under
View Detailsbutton.
Run Test - Triggers a request from the Amazon systems to the company configured connector endpoint.
