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
- d526883201e9c2fb2740ecc26e4be3c99812bff0977ecc530c7f234d2e2c5aaf
- request
- 7e9469a226c26fa4d17bb115cc918ae7545b0b9ebc3e5dfb12bf1d220f0c1d99
- transaction
- ce3e030dd386e91469c8411341c0d965d1d2d209e1450ebd96a90188363d5150computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11356
the chainentry 11356
- sealed to the entry before
- 3f1fab5c9a259ff2d72138f5b31a0567280e7b74683c0f25d23f93ec07fb54a4
- this leaf
- 84539e12edcb3a799179cf567d532e31ea14faa6d624667304bec7a5df7bdc8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hMBePVCA+5X5L2VJThJEZqiKWgu9N+qC9siMvTgVYiPLFy6QdvHDJuOXedwRTKGG4vEOyDnbOXKs7OA8+D1GDw==