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
- 1f7c4fbbb0c2480712cd8668ecbd96eb767354bf7896b81c2160f1535692bee2
- request
- 6033610f10b54d66496eef514712cf596f3fbb15613feb2c10b37d7f86175aa0
- transaction
- 22d76ce8d0f371f08f163c15a4b20078b60b62c6245415c429b8d3e9cf0a0556computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17936
the chainentry 17936
- sealed to the entry before
- 5ac3c5013f371956f8bfa5f732fb3e68acb4467b4d5fc73f670be7b659c83317
- this leaf
- 3edc8fec8f9c84d23959a1ab574f5b5dd9a35cbb721618c9fcdc4469f7fedffc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eXui5b45TrgMooBhlRxK9IEkUW3eLUWAW6tWmG4U70i25kDmje2+CjemXJMQaTu+HjaKuX7Tv5JWoZx63D5ODw==