.svg){kind=icon}
Prove Payments eases consumer friction with passive review of payment transactions while creating trust for the app (or website) to accept a payment from a debit/credit/private label card relative to the device, identity and payment profiles. The app owner can make a determination on risk presented back from Prove’s checks. At the completion, a Prove Network identity token is created or validated.
PV2A’s purpose is to create trust for an app (or website) to accept a payment or receive funds inbound from ACH or similar services relative to the device, identity and payment profiles. The app owner can make a determination on risk presented back from Prove’s checks. At the completion, a Prove Network identity token is created or validated. This flow is shown as a customer experience, though this can be run silently/passively by businesses in scenarios where funds are to be received but the customer is not present while this happening. Possession of the other account is not confirmed.
PV2B’s purpose is to create trust for an app (or website) to send payment or funds outbound using ACH or similar services relative to the device, identity and payment profiles. The app owner can make a determination on risk presented back from Prove’s checks. At the completion, a Prove Network identity token is created or validated. This flow is shown as a customer experience, though this can be run silently/passively by businesses in scenarios where funds are to be sent but the customer is not present while this happening. Possession of the other account is not confirmed.
PV3’s purpose is to facilitate an easy, frictionless customer checkout and control transaction abandonment where the consumer is not logged into Prove’s Network via an identity token. For this use case, many consumers will select “guest checkout” on a merchant’s app or website or not be otherwise logged in with a verified credential (no Possession + Reputation + Ownership confirmed before checkout).
PV4 is intended to minimize merchant fraud through a secure process to validate promotion or coupon abuse. The tool historically was used for betting promotions but can be applied to coupon and discount abuse.
Prove Payments helps card issuing banks minimize false fraud claims by leveraging the Prove Network for information related to a transaction to prove or disprove the owner’s participation in a transaction that they have later claimed as fraud or unauthorized.
This use case is intended to be the classic Prove Pre-Fill® use case but used for onboarding loyalty accounts rather than a credit application. Prove Pre-Fill® expedites loyalty account opening, helps control transaction abandonment and reduces friction by pre-populating a form with verified identity information. Depending on the merchant’s risk tolerance, it can be done as challenge-less or with a DOB challenge.
A complex use case by which a customer checks-out either using the Prove wallet or via the merchant’s checkout process independent of Prove. Once the checkout “buy” action is initiated, the full suite of Prove’s services are invoked (possession, reputation, ownership), in addition to advanced data analytics to match PRO data against the device used for payment.
.svg)
%20Desktop%205.svg)
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}
.svg){kind=small}