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
- e0a2ae1df2445e8ad18d87c4dfecd3fcac494459233a7e853f2c69d46d418067
- request
- 14545b73cbf19ac91a0dd15dcebefcaa45860c9aaa4739db48fbc0b20bb78a98
- transaction
- 310a755d755a0372df3bc8fb9d1647cb9e375fe169207defb448a774a94fd4aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52469
the chainentry 52469
- sealed to the entry before
- 7ec8817e15744876804e2643e4e01a583413e780101221e569fb4311e6a5bcc7
- this leaf
- a7094a55f1c448333950654a5572a196142960a2886600254df94487bdac7a5a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XzUTWECZZgo3OgPknUiLCCZt+BRT7KlSsoo8cSGPv/XNOtr8FPRMv2ZltzYZDVwXk6IxoKAWmOTUyNOCOYgEBA==