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
- b558baa634909a1bfda86cbb1ba65f98a4015c48cc74991a96252071b141f55e
- request
- facdede088d66e28fcd67a75caee594ca573b547daf362783fd8a0f40a539a57
- transaction
- 4567111b8f7b440f6324d55b5c1ec6bd4382a112ebcec9b7d915657be412c41dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46662
the chainentry 46662
- sealed to the entry before
- 0dcdf0b4373ceeea91d0fac3b047c32b6f3633508ad77f4663d0b7fd6402a878
- this leaf
- 14ef4952e5d7457b325499ebaa6edb31c55ad3b05f27483bbcabc127f251288f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WKreIIQpHRjQoPdpKBrvmWTGGYQqnOFPrTTVkddSSk10BqAWLs6ulacB7cNBFNHN41hFaAyLjUujCzVgEHFVDQ==