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
- 955a5713e42c86fac233de597dee28f70beac3d5bd49a265d490ae46f450c068
- request
- 527af732d1384df15df34f163723f8da4b2341e650a1ed0b47a639eeac82daf0
- transaction
- 3a55fe0bc2dccea4b1caf91cce35a0d22ff8f324416c63cf6a316a3d820fc21fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7863
the chainentry 7863
- sealed to the entry before
- d03290f6a55ae0db19bdff39a36aeb202429ef078d9fcb1abb12d2b4fd7ec503
- this leaf
- 58380d5555146d63c095c0b923a4378970d04ba375376331bfeeeedc570d6694
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZYbTWQfSoE6/le30ercyDFCnbD6gwaMOj5V08hfVB9HSN8s/W/aQs8xqbftLqoTtohFemZEJvlSJlRtLOj74Dg==