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
- 5924d6cd0f6024e7b3005809208ab028e225d1002c2f0ed346bf290fa80aca2b
- request
- 315825480d6ddeb12a8130294176ba6e3119eb82f762019482de81881cb97b8e
- transaction
- d9ed90bdc789981b444c6e7aa6dddef4d944fb4e36b876b9d850116469dde054computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30087
the chainentry 30087
- sealed to the entry before
- 568cc372f83fe76690d5a6e6f86319ed2e1061a50e6e4ec41c771714fddad389
- this leaf
- 98b51327926b649a77ab0305661a4097c2d860b536126a38e6ff29c6ef6d2016
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a4EWgqTy3+HfeBRzlqkF70aRJCVjuKFDE+vB+Z5CiqRugvBgtGsCp5OZu0lzDzFoxs3p8toUF+dTeYxpJ2iIDA==