why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 0c52531157be01bd6645d1bb423d17f91742a0fe10f008e87512ca4cc7618fe7
- request
- a4bcb54e4487a75e494cf94f71b48b3ec9807fd743cd50f90fbb2b9b9f50c078
- transaction
- 844018067961d964e6512c68119c8dee1eb0dd6b11797cdbdad20ec137eb743acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10790
the chainentry 10790
- sealed to the entry before
- 298c63f47124ea6373bd3759f1b11c0a05a4768caecbd63b1316aff635776430
- this leaf
- 0749a326d455a9c0ac1244de8128676bbad1ad5b1f064629e74621ddedddb12d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JUYG9W49Dip/En3R/90e6utgWLj6p31Cevacf6groLwzhdpnjS7F8mIvQ1woM1zwDhHOTZCdILS5W5+HpIUkDA==