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
- 7c87e576d3a6e7f4116c02997c893728de5739af1aa32932204d48c8969468c2
- request
- a4ee6aefc5c343f854e75e986e214073c38390641129251d0e972bb534557744
- transaction
- 4e36f527ea1079cc53723ec7cdb960c93aea17e89d7f21f32f9291582ad5c27ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18151
the chainentry 18151
- sealed to the entry before
- 16a1aa8894b3c9cd66c5ce29dbec930d5683bc394925d2263d6a56cea1f29274
- this leaf
- df13a7e8121409ac00ac80807bdd802040d8e3d7a587a34940619b060356c4f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JEA16Q0yD6htkIiU9o0IVrXsYeBGigjpGLn7PRqrMwsXxSPMhJFNDR3XuDHsrDAjwYxMGcDz4LCMrpI6qrWiDw==