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
- 2c0273b7dfe484467cdb2dc6415c7546e390e799e827f413010a63eb102a90c5
- request
- bace25d4a829265efd646e2af34a68e17df7f258f1549bfe28f2f9e51314cae0
- transaction
- 6fa8183cfebd6fce1d848d872e061d222edf51c186a408a82893237fdf45304acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44052
the chainentry 44052
- sealed to the entry before
- 91baa0bc0ea98249524ddfc1dc3e1ad079074de2ba3126ef94587139237859eb
- this leaf
- 1de14d76b3f55b04e5bdef5cb53238e603b6c8ad309204a12e2ecdf67da3132a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8ZRGrcTFe6P+Ubsp+HzldFzmsTNyFVDSrknmlTEWCIR6dhBTA/MsySabCBfBirTNKhwicGK2C4Q5XBAqGkNoAQ==