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
- 74a6f26efd729437a4aab399830d159d6aabc6320f1cc80d923e4d8c964116da
- request
- a13d707f9f23aa6b42dec1e724b638509ea1169098e11235f7a8f210fc9b4385
- transaction
- df07e99491f51e862106610d3e5cab13f6a8a5f4f6d57320eba1eb25e7ab3010computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30103
the chainentry 30103
- sealed to the entry before
- ae9b1d3b76c89586fddcf09314a2b2d733f35f91d8784c1110f2c1c13d48535c
- this leaf
- de155dba6a205651e44e26e7c2d7ce6bc99c7fedcdb035f8bf8c93471e9a674c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LzwoEAtMQrtToZyLIYNOkg5pxn7dwife1oPm3y8ZptaSITdx688J31K2ljHB5GiFV0EciQ6BOpXCGJX52x73CA==