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
- 41209d109b98a3aa434803c2385c490a15fc4fba90d31f7bfd8f13b5c888df0a
- request
- b98ebb66464bc64833cc33360cb52f85bc5fe66f10f3c61040e8ea0b96ba0dd8
- transaction
- 96a22cbfad6bde409eea9a2f1331ea792eced604c88108a6a3bbbbc6e7b84721computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21856
the chainentry 21856
- sealed to the entry before
- 012e2cba9f25e54cf9f72d3b031f4827c9e549fb5854429a9f3bb920da76c869
- this leaf
- f1eeaf06736310f3350fe8302f66df6ae323ca95c66e0d36b164762d2128ca09
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VGA/b8U2nHBaim22BmIFHbI45AVI5Eglgs+5gqwn6r27WG79CzgNgFSOD1WbsgkUFaepBMDUowO3QfYmToGNBg==