Skip to main content
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
  • Reject
  • Fail

Payment methods

  • Card
  • Apple Pay
  • Google Pay
  • PayPal

Instructions

Set-up Instructions

Required fields

The following fields are available for passing to Primer, and on to Signifyd.

Testing

When using Signifyd testing environment with Testing Teams,
  • To trigger a Pass outcome, set metadata.connections.signifyd.purchase.userAccount.email to testapproves@signifyd.com
  • To trigger a Reject outcome, set metadata.connections.signifyd.purchase.userAccount.email to testdeclined@signifyd.com

Mapping

Base mapping

purchase.totalShippingCost and purchase.shipments[].destination.* are only sent to Signifyd when both payment.order.lineItems and payment.order.shipping are provided.

Fields not currently mapped

The following Primer fields are not currently sent to Signifyd.

Custom field mapping

You can use Advanced Metadata Mapper with Signifyd to map any metadata field to Signifyd’s requests.