Payment card fraud losses worldwide exceeded $32 billion in 2021 and will continue to rise. Protect your bottom line by deploying a fraud service, like Riskified, to stop bad actors from making it through your checkout
Primer supports Signifyd’s Checkout API. The Checkout API is to be called both before (Pre-Authorization) and after (Post-Authorization) a payment.
See our Fraud Overview for more general information about how we support fraud prevention.
What is supported?
Actions
- Pre-authorization
- Post-authorization
Resulting decisions
Pass
3DS
(pre-authorization only)Reject
Fail
Payment methods
- Card
- Apple Pay
- Google Pay
- Paypal
Instructions
Set-up Instructions
- Go to your Primer Dashboard.
- Navigate to the "Integrations" section, select "Add Integration" at the top of the page and search for Signifyd.
- Find your credentials in the Signifyd Dashboard by following the below steps:
- Log into the Signifyd dashboard
- Go to the General Settings
- Copy the API Key
- Follow the rest of the steps to set up Primer Workflows for fraud checks.
Required fields
The following fields are available for passing to Primer, and on to Signifyd.
Field | Type | Required | Notes |
---|---|---|---|
metadata.connections.signifyd.checkoutId | string | yes | |
metadata.connections.signifyd.checkoutId[].coverageRequests | string | ||
metadata.connections.signifyd.customerOrderRecommendation | string | ||
metadata.connections.signifyd.device.clientIpAddress | string | ||
metadata.connections.signifyd.device.sessionId | string | ||
metadata.connections.signifyd.merchantCategoryCode | string | ||
metadata.connections.signifyd.purchase.orderChannel | string | yes | One of WEB , PHONE , MOBILE_APP , SOCIAL , MARKETPLACE , IN_STORE_KIOSK , SCAN_AND_GO , SMART_TV , MIT |
metadata.connections.signifyd.purchase.products[].itemCategory | string | ||
metadata.connections.signifyd.purchase.products[].itemId | string | ||
metadata.connections.signifyd.purchase.products[].itemIsDigital | string | ||
metadata.connections.signifyd.purchase.products[].itemName | string | yes | |
metadata.connections.signifyd.purchase.products[].itemPrice | integer | yes | Price of the item, expressed in minor-units |
metadata.connections.signifyd.purchase.products[].itemQuantity | integer | yes | |
metadata.connections.signifyd.purchase.products[].itemSubCategory | string | ||
metadata.connections.signifyd.purchase.products[].itemUrl | string | ||
metadata.connections.signifyd.purchase.signifydClient.application | string | Example: Primer | |
metadata.connections.signifyd.purchase.signifydClient.version | string | Example: 1.30.0 | |
metadata.connections.signifyd.purchase.userAccount.aggregateOrderCount | string | ||
metadata.connections.signifyd.purchase.userAccount.aggregateOrderHistoryAmount | string | ||
metadata.connections.signifyd.purchase.userAccount.email | string | ||
metadata.connections.signifyd.purchase.userAccount.phone | string | ||
metadata.connections.signifyd.purchase.userAccount.username | string | ||
metadata.fraud_context.device_details.browser_ip | string | ||
metadata.fraud_context.device_details.user_agent | string | ||
customer.shippingAddress.firstName | string | yes | |
customer.shippingAddress.lastName | string | yes |
Testing
When using Signifyd testing environment with Testing Teams,
- To trigger a
Pass
outcome, setmetadata.connections.signifyd.purchase.userAccount.email
totestapproves@signifyd.com
- To trigger a
Reject
outcome, setmetadata.connections.signifyd.purchase.userAccount.email
totestdeclined@signifyd.com