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
- 44ab57b01db636412d33873c2bfa5935d2ef71ee44e9dc971f8228c57b965f98
- request
- 0b5e92c1a17abf487d26ef67ac853aa84c94bf3e9b89780dff7998bf71cbaabd
- transaction
- 734145d03a08ec636e38c5aa362bf5536c02184db067cc3892ce587103c24060computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36382
the chainentry 36382
- sealed to the entry before
- c6b4dc690e82fa1043a225828b4c2ecb741e823efabfd3dac68c0c44d6951dfe
- this leaf
- 762c32ce36fa839727135cdf06979a70edfa02232e6945aecb09ed0ce085b91c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /0xsEpFDvz6Z1LUYuAAal7t5q9dnM+Ow11CDcLc/Gs9KwFqmEvM6MHqUvRE/nbAaKwFhYl06I48oEjcSz+L0BQ==