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
- ea05073fcdeca04f8817fea3b54ba06ce8360f7ae5f7047c04eae096c8f6a8e6
- request
- a69ee594d53f8d2b1906b391d0df3c2307493c33a43f4fd2713fdebd8e38a66e
- transaction
- fd3b65ee54b9fec481a0ca0b2881ea66d9064f13b35a4b740096623590d024f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1705
the chainentry 1705
- sealed to the entry before
- 28fa15ad11efa9cfe9d2ba7cb00a7be89fb8700381dfdfbf26c716ac09ebc55c
- this leaf
- f2debd521779df293ecbbc01d28807c99cae145e03b335e8a342fe91a7ecbf8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q/TlQBbb/pas+WPZ8OeoEPcKORsOO/PSEntpDPG3JlUw8TYl6sFjrQaV6AXxSGkL5Q58eect25gacX4Td8OZCw==