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
- 45bf6aee7ac5dcf9fd50625b174049ba4118ab2ccf1c00994ae13fb6ecbebc4e
- request
- cdb132497a9a6f3cbe9122d35b4421fda0686f137f970990a90591145d9db470
- transaction
- aefb7f5a6c28ed0281080d4ed2f72a0cfc08ae04a0188dc3dee3a7ac85c992e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71123
the chainentry 71123
- sealed to the entry before
- dd7af207442669df2c1f5cf595fea04b798d18373358902366c3e9b8db90f6d1
- this leaf
- d3ecc0aa2830e5d75349638d4d9b817d1a57c29b774b45c0b146ea43730525de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pyq6k8ONy4TLUtSYhTRp7FrMLLR04ehiSAYlZV+025Xr78ujhC/1w5Myr7HZuiJ3V7jvGWBnklutQ/TgRMEODg==