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
- 4b5ba1f0b349ab29d1faf4c85d81bcd7495a3c05d9a4936d5dd71ac8dcabfe62
- request
- 6c3c2af144f49096273655e6820fe0e4ba0d022f1a4f83edbda73d6e20af5a85
- transaction
- 3cac84cbf8dcce74aab4e29e4522970961fec0d5596b711afefdf332de60240dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72286
the chainentry 72286
- sealed to the entry before
- 12b0aec2ecd9456057116b255e6d0726ae5d12aefb6c740742b87c34233a517f
- this leaf
- 41db80c2fe6538189d54b3d9b0bc5c658f71b48ce1889f35734f8a70244f7cef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PyT931w5FGJU7o0c0+Uw5OCeJiFLTXUWKLMDjh9Y79xbojKGNy5W/KngNZpdIfONnjkAMa/WPnMpE7b/FWu2BQ==