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
- eec43f86c6e46fe1bcc0ad08f77ae7466f174cb94da6560564e111a63adb62d9
- request
- 1108671543693075802cd1d026addbb99ccb9950b9013a029df188eb8c054079
- transaction
- 396fb99dc6d82721bb9270187d703202aa5eddb0148fe0d2cfb52cf028a4ad8ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25208
the chainentry 25208
- sealed to the entry before
- d53f78c5bfb24582d35c27ffd7bc97c35b12637c9602a7bcabc575ef672310eb
- this leaf
- ee90bfd0215e623293fef3e2d4bb0ff7bff9c4e8312b8a3ec04d866c88f0734e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AYEyqy7C+TYobD29KwJim8akWqDBsj5KYiw1/b2sira4wd+oRWd743EUwWMLVcA7/r8irx+JZySkJCUmCRsNDw==