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
- cca4e7d2d57c89f284415753ab72a65043cdf7e9d085c60110147c9554cbcedb
- request
- 0d5f49b2ddd0f4a5e50a480d3fb2c4ae02be465ae664f045b88afc2911a62bb7
- transaction
- 89eee69b0f483c3a4a30692162f8e38f6cb41a602eeff19f15cebd0f410a9e70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41611
the chainentry 41611
- sealed to the entry before
- 2a3535fda11051c9a663c75b1158973605c7688cfa812e54847d1289a6038db3
- this leaf
- 3c7433f809e27cacd45051be089c0f3130fb1a82fe8a5c15c8c7bdcff7106199
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9z2gXoZZzLMt5lC6t5qcnXluEZk1MFPvsNB+JnKRAr4pOoJvoDA8v89kFw8quulgiqrNGJ2e/p0KzqCWzlQ+DA==