faqs

What is a Customer and why do I need it?

The Customer API stores a shopper's personal, shipping, and billing details so they can be reused across payment requests. A customer record is not always required — some payment scenarios work without one — but in most cases at least some shopper data must be provided. Creating a customer record up front makes it easy to attach that data to any future request by passing a single UUID.

Where do I use the customer UUID obtained from the Customer API?

The customer UUID (returned as id in the Create Customer response) can be passed to:

• Checkout API — when offering PayPal, Klarna, and other APMs

• Ecom API — when APMs or 3DS are involved

• 3D Secure API — to supply cardholder details for authentication

How does customer information impact fraud scoring?

Verifone's fraud screening uses the customer record to build as accurate a risk profile as possible. Without a customer record, fraud analysis is limited to transaction-level signals only, reducing the quality and coverage of the fraud score.

How does customer information impact blocking rulesets?

Certain blocking rulesets rely on customer attributes (e.g. email, billing country, phone) to make decisions. Without a customer record attached to the transaction, those rulesets cannot apply and will not trigger — even if you have them configured.

How does customer information impact reporting?

Without a customer record, the merchant will have no customer detail visible in Verifone Central reporting. Orders and transactions will appear without any associated shopper identity, making reconciliation and customer-level analysis difficult.