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
- 0bf5022e600eacd793e03b76a45dd3b7fba8eb2e06e85b1825bc8f98ca462c38
- request
- b0f1a18db305d590bfb4610b57111d1a97876667d4ec67acea2e577b0e16d450
- transaction
- 2310d5a6d332dc4e3ec2bc28e3573bb573e06db4b5f5b4406255e0da0e32ee4ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62099
the chainentry 62099
- sealed to the entry before
- 4afa2fbab98b324b834be88d7f00ad813fb987a0632d804909ee32213492de10
- this leaf
- 9fa50873167ab70073f3d01388afa381a8b44f55784b04a237098a71b24cee9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- un5uNMhMHkzVBbjXd6adOqTEEjIJskKXN3Rj/fU8das4plVCgyTrFKv++tvfJzsbTAuZSYfS2z/NBV+8iuQbAQ==