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
- 993efb0151d537fc3742126ce4968165b58879cc971f06a3a1e98381bda1c0e4
- request
- c95df5f214af70a37167b16b97f7f8a39b698165c2f60bc80ca63b9114cabf9a
- transaction
- 214c28bc192d3df2ddde2af2a46a4fe0f22da22c45462118d51dc7687d12249ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35291
the chainentry 35291
- sealed to the entry before
- f20efa2b672d50a6c31b8647b5b3fc4cff3470b23a272842e6fb88d165242e15
- this leaf
- 16be40d123331644749b688b3739d2abbb07c3f2e4fa75b71e61a286f39d3a41
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iZ7fXETIe5eWnOXE0i7xNmJMsEpzIT2V1gqNV0XWTev8seQLkLnLJ2fnvL7UwWROTDJngFJeGfOXtyqNVTKfCQ==