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
- a4f32fadedf88fbbc75f0acd5a0d9dc94eaaf7e7f3448cd659b215b9ab12e753
- request
- 48f90794f88114770c9b690b4ae8301f53921d0282443c4ddd6278632c749bb6
- transaction
- cb5e9f8321c2f7f01e9f6c5b603ed17cf608375662d518cff8fe0107247eb18dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66577
the chainentry 66577
- sealed to the entry before
- bea0ddfbf55ad783128a537e56fb1f4d259b4c3ff2dd44feb50d72ea37c43d43
- this leaf
- c796e016ae5fa72b2fdccd2904c8071cf3de8d772a998a5475e046065ba7dbf4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2PEDE9vTK+8VySlcA4gKyiTGJIpQOlWwRGmXHW6zrOsi64ufCqOWAGm3ss/so6lDS0e7hP15zb9okouz7DrBBw==