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
- 80105a75c966bc0b9d9fbf182e34f74aefd8a1645e876587cbaaf4fddb264ae8
- request
- aa262befc0e8a5421f2b1777cdd7290579ac497e7d6bafe1554ee86bfc5f282f
- transaction
- 74f622617e7cbbde4e0d18858b85a898af97b3072240ada4c986f529585e364dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67269
the chainentry 67269
- sealed to the entry before
- 866ea7ce5b2b632cd0d082fec6c8ceff0aa48fd1d48f837b41a1fd5a988d237f
- this leaf
- 907ef215f61cc81a15cb73c711a6e7b6377927d56cc3b4fe0f458f3e78d075b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7iSwwwUYF2m7kQqvIN+z7DV6iOlp789qIMbyM7vw23ZFViTlWNn0KoHJnPR7qu4cuVvou8EAOyJy2U16g+uEDg==