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
- 31327f1a833c1affe5984877e8280f82f36775c751423efa0152e6b7666390f5
- request
- 399011c3dd360eb8748769c558c485e1dd4f5343b4f7db3c0e52a44cbb3ecf21
- transaction
- 9f708bd392d433cf2aee6f71399e844706dc76c05a0b9979d567f56e61e5ef86computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51700
the chainentry 51700
- sealed to the entry before
- 66d5bb57e07258dc8083d5fd9eeeef53f4d8c039b52e4310513ac7d80e4cc321
- this leaf
- 2eb484e3a752bcd544242f75f1f3a42560e8b3ac8eafc04c0d71118fd1965797
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UyzZGiWF9gQILaeGhP2BN6tmgYByhDm/bd5ZKEWCsHaaNSGNeqj3SHbFqrUsTQBnv4ELRJTaZfEAHjouXWHbCA==