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
- 01f15bf9a5ac8c38c57481d424886a7e63183f0cfe0d852214ea7c5606e28c15
- request
- 96acff78a45b5a5cd2086f46294f29e8c57526833ee4bd11b7922e71869bb6fb
- transaction
- bfc2ed6fac9f11cabb8a41e71cd073240a2bddad0ee77b08007a9584bc10ba85computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10597
the chainentry 10597
- sealed to the entry before
- c1ce873a7097004724d758c7ee6d6eff1441aa1199dbe053a7c5bd44cb0d628d
- this leaf
- dbcb5b913c5fae2d08658ca376515f432025da4d17f869b93e532f1109e87da9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rPVbW6mXLv/iPu3HHUAdUlstvyGFjdlzX1lgMbL82u6aWRymeJG6LRNlPpD8IqsUn7lgnrRH/jXLyJuOdboDAA==