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
- f630714a531a649ca6a83c58b5eb0df835955d4cb244d8495a696d77bd8fe243
- request
- c0cc41583fd9c19fede37f678adb48238fb871b2964856f5b388f94f55588b4f
- transaction
- 2861b37b4c766fe700febde351c9146183ed073ad203819937897be89ba4236dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1132
the chainentry 1132
- sealed to the entry before
- 4e8a98c081f6e342fdcc978ae17519bea9a699be08bb40469ec4f6050c04e223
- this leaf
- 8ef2eb992a998bf6c841556af69ffc14e11afa5c176a3624b79a07afefacf2da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UjPIEQlC6dWpVEGwGCQHxyo/Cy7B7E1AUv5wFeEcqXu4lFuQk/hamflKRFSW8Lxui7fU/LXNmcA+JyE/klHtDg==