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
- bf69d6f858e71de008bebd03d91b2cb0db729e51444cc75b21dc30be0984aa37
- request
- 1794502bab246f60333bf336d48123d8d25af9f327ade0fffde5963f623cfceb
- transaction
- 72415b9be0586818fca12087eb5d87b5aa06f603c584adb67f19b43724382870computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6485
the chainentry 6485
- sealed to the entry before
- 3fd1a3d4f3769e12bea83a6f1b91106b5a0d3ff3a2b62511f204ad45466971e0
- this leaf
- ff7a9dc823c5af32979ec331f489915ac2ac030826e3e96ccadd5e97c23bdd40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /a2WVDmHqcaGrIA8YqTI8xIG99NvlJauhZRrIGA5wZPHaZ2vhf58GQYjUpDLS/Ntl6EhquWPNyVrShLsWOcCCg==