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
- 27e6bc0cb977412ab905185ca70d59a6d10b922f50639c86b287195fd8fa81ae
- request
- f7475d79efe8e302be4d68c7baae9348c0dcf333f5d98ecccd7a7f60680f8631
- transaction
- 40aae3aa0c6b8585b4010b1559871e0964efcde938328fc24de02a56948cfe47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63767
the chainentry 63767
- sealed to the entry before
- a4031f7b91f58687b6f1eb68a5e7360631541b224fd6852b173a6b638cd31894
- this leaf
- 2841fb5543f99dd4795c085dc8ee3927041e342dac925f2652e930b47061b5cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l2vA9aCuesMk2a4/FA1AXE85tUSJa7al+XObiMqdHrFS3zZ3zVJBz+/auQG3Nju5AIftLKarEI1d4BrWZbhUAQ==