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
- c5d37767d7b20bde59ce70766d1dbd8ee2f3838b51c461b5738c5e8af6efb718
- request
- af947f3d192f0571ecf51639b7078f7760d995b87281266fa8dd82ad51bec58b
- transaction
- 57ce57415ee70f4010256bf3099d591e04a744a8b73389b13fbd40d757256025computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68865
the chainentry 68865
- sealed to the entry before
- 045eb88f8ec35167628994bd292febab1d17eeebcabac57f2029ef04299c04bd
- this leaf
- edbf3fd401051c6f2ca0e8827d4cc0f2a4b95bc1b4769b5570faee283c6187d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eElyYXVMuSH/3567seJXEH5RhltzIxgsPQhjxF79F/Rkcd1qsI4IesmeXRyIsTvJkZtIjDpjWkcTSYMr/kFGDw==