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
- fe278293ba5e638f89017da93b050d7b3ac55c019041fb89075c0a5e4464a193
- request
- 9b26338228492d1c874f32bf78e827a29615ffda65eef427f06361340255e694
- transaction
- f4708a8ddbf33f726e309b0288fb98c0c104d9dfc23bea56435b67037a1ede43computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45909
the chainentry 45909
- sealed to the entry before
- 3302c317436e13c031246717e5bb33a81b3c32cdf75be0258a0c1161b898799f
- this leaf
- ea20d91bf901e1793db5690ea1cda8f45e98fc3433b990d353d4434bf753c14d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4f1h0rp9EVwVnCCpRsAw8bj9q/nwmflWxBg0kqMg2XVThHVVa2MBIex0Ma0l7I99e3W8q84UlYSNTBl7cfxkDQ==