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
- 8c69bd079e98e8f98e5c8cde27a5094e12d498b7751ef2bb99748236cb557033
- request
- 73b1c7565cebd1b56b0bcb38eb31f05c4c69e7a383a98a170197b916ccbeafe2
- transaction
- dd7bed3c97ac2daab92171cd47514374bae95df309ddc73290550ce3418b4a4ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51510
the chainentry 51510
- sealed to the entry before
- 0029e3429ef9e24b67ff1b7840b9b450ee7daadba4ccfa2d63acbdffd66346ee
- this leaf
- 0972beb8c5f3650c8774180b05e332f3c44336df8b0ba586fb36b94dfc9db27e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kWZuX+X/H4Gg0srcCakZkarcT77gKrF8W71je/JAsQsfk7dGz/6AoGfkDE/rzvRXMM8nBe3+qcEzljr3PV5KAw==