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
- fa8fabb924025b330742eec79a645404f7a0b5ff35c950c42bfd6499681563cd
- request
- 15762ff95c2febbc56c0d6821491b40320abc2dc61c78d584c8ed03db95eb9d1
- transaction
- 02cebecbca7e2cd57a44481709e856b0e4dc51875f8fbc145e99e41f8b116512computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60361
the chainentry 60361
- sealed to the entry before
- e32e9f5d5cf9e07c4e0ae55d7f1b370c9364110b89520abb23b760adbb7dd33f
- this leaf
- 9e6ceeb7c206cfd0979454c5de20dfe3b4f18fd7c2480524a5545e458c63bf3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /8H2QikEhgKAnLzwoZoj/7w5HfPv/bA9Bc+uwr6x9VQtoKxtdUWdipTwS+gayZTofoP/PO9ZaskpSuJ+HobZDg==