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
- a91a25f8a939b8a52af123fed6081a4b464f55e3c4f91eec2aa3144712905833
- request
- 5fe2e53ce92965ffe4fdb6a90980bd3ba7cfde0b9c8e88faca0f062338e63799
- transaction
- d1938ee030f6d025858a4ff7ffbad4b4562d4652d1efc3f0f8588e1d63e5aa1ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66922
the chainentry 66922
- sealed to the entry before
- 8ed981c4f63ce1675ec8b57978199e10fcfd469ed4964d3c4b5df93010885258
- this leaf
- ef9c13dd2e234fb240d3f2f49c6d4caa626cce52f882e5b1bfabff345856a7b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2jNX6ElsP5iAYGsdpFQgw4XpuczjT4K+iRD/VXSsstN8jT98rOcd0ntQb4Y4qSjQWVUIAh1mcWpn5gvzc4ohCA==