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
- 6657395fc27315e5eca7af7deb8097dbe00e41623a628d548c94ea0747d5d20b
- request
- 7ea8452f6fc319c1b5fbce7d76cb61cfd52265efdb4156ed461199889922d170
- transaction
- bbaf41b8423d2097bd700e35218a37ceebc07cf0541bd12090811de9de0dda47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66736
the chainentry 66736
- sealed to the entry before
- 275ddb78856158c4ec06494034199c54590356bf1871011b3829a68fc5a47fc3
- this leaf
- e76ba74da99ca85cac1834068432856b629a0af4c9bcea91f0dc15925f0ee41c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2nJGK5yENBlCMLxT9efNL6YULMhPJ1Tbnbe2EE/sqw5Hx2+tjWHVcBvb+z4GAVzpZ2DcexfGWeWYjhYETPU0CA==