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
- 83ea345c2412d6ab23e0fc545e799cb486ab097e5ca52affdb363b3cc1775366
- request
- ba6279288a465370625a782594cc453fb6aca9b38bcc2d893050230d0e50aeec
- transaction
- 66728a9cc6d89fdcaa9fea35e088f386de16173538ca28f380c459eaa044822ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67434
the chainentry 67434
- sealed to the entry before
- 06f43f773b7052be1619b797f77c8afab7757cf7c61dbbe74ab2ddacbc801f3e
- this leaf
- 3e492bf30020fc4d1ca72ebe0f602e32e8da39863d00b3aed0dad39cf68bcd2c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sL7MT9ZZNw9z9olcD+oJtfnkxf0/oudj7pkz3nvezs9O/qzV0SOmUrzlgHrlkCFrlHBa4LrCyFrVXCkVC8mqDg==