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
- 58af735af0fdcdaad983530a1d95c41b9ee22261064322fb50501802f9246800
- request
- 9a1c1127d2a7e5ea22f488f37f6362350dbed68772cb9d1af73213f3ea2d0dde
- transaction
- a5ea71becfb96777349b95695fffce91bdb1299504e96a92b732fdcebf19b688computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29032
the chainentry 29032
- sealed to the entry before
- d025311b0f21f588dc7320e412587394f6fe178678239c64d187ecb64ea1c203
- this leaf
- 087a9bd50438a4b16859171a1733ccb2292b6098a5a6f9f65a51cb4d930e4aa4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pyp8aA0QUMxZeerCB4yD6RP5DjQtXPZyEtYAjtQFlVwF0vSYEPpiQGiErrQIga69mU/B4UiYZrj0krX29NOSBw==