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
- 559c10ee6703da7a94e314cdd14eee83683c741e07d725a16fd853290b242583
- request
- 4fe83266ff4589266767226de76a3b3029b36ff657fa0c39bb42c647207c30de
- transaction
- 941295403e4ae782409150cc1fe8999b74872d8d0648a97854453a22a6aa22adcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15074
the chainentry 15074
- sealed to the entry before
- 22a5e1396585b4405470d6737cb6a9f6978721bb204ec0d51894cef81d7de1bf
- this leaf
- 33d6069bdd93fdefc4427c02a52b70bf2c6824b5d62fcedc5fda68fa5064cb55
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YLL3LxgID6NjQLV3B/NNlxFsstML6TlKSk4+4AegOYQIKyNXblgdsZJRNq5aErE4EVZZA9bwYA4QT0ijNQBuDw==