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
- 27b5377f7db1e3705fb7e1ee38d1390634b4938e00fa3b18978de8c59af74567
- request
- 53134c69e9181d371633a544bb4aca61815ffe606486856cff18aa32806eeaf2
- transaction
- 8f23e4c0d7ac8ec303e703cac5a1607a3efcae00121217183eae8340c22826f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55583
the chainentry 55583
- sealed to the entry before
- d5a864f0cdc95be4211b8116d9db3cc8457ebad37ee687374876e8d801e938e5
- this leaf
- bbe43d9e1175b214d0d4cf4e243cbccf77748f14d5515a1dd167d1197f65bbda
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3pXMm1CaqRhY8hOEBUBhg/+QyKYKyIUXK+7nOzaE+qIfnuFW4Ce/3WRsmbkUqC3wTPaRiEw8SCqBblWQCiBjAg==