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
- 079d792a25adfb6dc91e923e1fc3ccc7a533653e1765cf7e0e55efef180318ca
- request
- 2acc3627913a726e1b02cbd0d02d7dafbd72338e5db91a3351f04d3df7148e47
- transaction
- 2bff3f3a246f314b1f72988d6528c07eb8e790af9f4cb1968350a255a38337efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31853
the chainentry 31853
- sealed to the entry before
- 69577fc25f01a2d91cb9e5de080cdb55708626ea2866ef9ab55b0b650968c08c
- this leaf
- 284fe286f1b79db07bedcdbef2bfb7ef55771ef65b4ee7a9958623809df5aa3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eRcNirBagi4HVOEexqyGgLftO1iNAKKn6oL7g0QiPuDb4IP3D/p7T3V6ZUMmhDCmOmOuM/aVEgdUUSFSS2sPAQ==