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
- f02caea706e6146034a7bc42be4ae02935cc504bdd2bd8f9f97721ccb03bf52e
- request
- 77082cdfec5596feb1bcdfd7a9d0293369958db255e12c08fcec112d72446a04
- transaction
- cdca99437063b8daa35af2f2edbba255202e6c42ede74e298a2cccb5b95c8010computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41160
the chainentry 41160
- sealed to the entry before
- f0883c9a1511e8b5a04aa901c0d46a62d0f79d1fe16ec2a4ec5b4c2ac7b0101a
- this leaf
- 7a235903ce52b948b3cefbc91470749e8e3eb316311cb040b7da1f8c3c3da318
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- enkkwrq2av1Mq8rNgK4xrSbCuNgfv4f+neL3abbmoIy71CnxHxnqygG607os2r+O7ryib+3wOObPFg1OWlZDCg==