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
- 64c06c9eb4535dcbc473a61675ff14924e4545e90ba60ff055a7fc64dabc9209
- request
- f41db3e75209a88771049d72f96f1d7f42a896ba3990a426514265117e0a5efd
- transaction
- b26ac2378347f3fb6e65ba607c1bd67e45a9498b90c68d746993bf5e30bbd613computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42815
the chainentry 42815
- sealed to the entry before
- 35d355b921fdc4750ceea9d6a3a711c1f9c84bfbc0a5e2fb6f5ca82145176984
- this leaf
- 104b4e13f3eb8ac11fa440a4306e7aa4cbe17615a7a41200e166ebf058600baa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qHzs4pvhLSilMxGQUKuN6r7z19TQjdnqwNcTPQviAbabt/Xfl1nOl7/mNBQrJZOZnQFxAwrMqXW2s7rIleg3DQ==