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
- 6de1d8a5ef9d0a4ece3d28ac555e1a8dcb9cf3b6af64a83c4564f4241588f1f4
- request
- 697035adf303dfe7ca5d506eddcafdb59149e7cdd1114b98c974b1cc1672da95
- transaction
- 33cd4c743453e75331ff9f2cf83393281cf0ea9c4680a77d6c0169441134492dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55650
the chainentry 55650
- sealed to the entry before
- 2857f6367c748c6b46d3a50de4934f8359b3a06662c85df090442c7676ef7bda
- this leaf
- a67a1c71a42efec1f51aa9d933f49804381e175d232925becc1eefe9bff05aaf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zYezskpmjOCDpIDZqNQn/66noI4EZMdSacqszn2kemCtwX9ii8feIa+UlMaAdkSFEX9dkRhr4Dz/9oUzlIRxCg==