A payment attempt is the try recorded on a payment link, payment page, or checkout session, including the device check. A transaction is the card result in Transaction History.
Who can use this. Open the link, page, or checkout you created. The attempts page is reached from that record, not from the left menu.
Before you start. You need the link, page, or checkout session. Permission for payment link attempts is separate from the general list in the permission map.
Steps
- Open Payment Links, Payment Pages, or the checkout session list at /dashboard/checkout_sessions.
- Open the record. Choose Payment Attempts, or the attempts link on that record.
- Read Fraud Analysis. If no device check was stored, the empty text is No device checks yet.
- Use the columns Timestamp, Decision, Suspect score, IP, and Location.
- Open a row for Visitor ID, Browser, OS, Device, and Risk signals.
- Use View transaction when the attempt is tied to a transaction id. That opens the card result.
| What you see | Meaning | What happens next |
|---|---|---|
| Decision Allowed | The enforced fraud rules did not block this try. | The card result is still on the transaction, if one exists. |
| Decision Blocked | A block or score rule matched and enforcement was on. | The customer was not approved. |
| Suspect score | A number from the device check for signals that looked suspicious. | It is not proof of fraud or of identity. |
| IP, Location, Browser, OS, Device, Visitor ID | Reported device details for that event. | Missing values are not proof that something is wrong. |
| Risk signals | Which signals matched. | You cannot edit those rules in the dashboard. They are not a merchant setting. |
| Invoice, subscription, and Virtual Terminal | Those flows create transactions. They do not all use this attempts table. | Use Transaction History and the source filter for those channels. |
After you save or submit. Reading attempts does not charge, refund, or unblock a card. To allow a later payment you send a new request or the customer tries again if the link is still open.
Example. Example only: a fictional payment link shows two attempts. The first is Blocked, with a browser and IP filled in. The second does not exist. There is no APPROVAL in Transaction History. The customer was stopped by fraud prevention, not by a successful payment.
Troubleshooting
- Attempts is empty. Fraud prevention may have been off, the customer never submitted the card, or you opened the wrong record.
- Allowed, but the customer was not charged. Look at 3D Secure and the transaction response code.
- You want to whitelist a device. This dashboard does not include a control to edit fingerprint rules or to bypass them.
Related
Found this helpful?
( 0 out of 0 found helpful )
