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
- a2f1dba68592b1b2465cb1606d6eeffa97d40b35347bf67ba5544a042ed29ea3
- request
- db115cbb19190bb0b10bbb23d9907bf21ed68095f4e0e8db636b5e732df5953c
- transaction
- 21bc8560e252b8014704e7b1de6a52606727ecb8a769769903ad6a9200f63e22computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6460
the chainentry 6460
- sealed to the entry before
- 5f02edd8c0ea90577b9d9e2d2e812017b447b36ae63c81092bd573980f432c47
- this leaf
- 926bb4c5d96fa2759b021086a400d6c08b21513f6b007ba907a9f02cf620db32
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ov+pfBxaFaMP/+OJJ/NoHT5pT2i7wBhagU+A5G18Yvkpd8wxh4R9xyC1yFLcC6GS4TTlRo3qiRMCdfeXXpT0BQ==