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
- 7e4746348a64da94305e09b36641456923e83c55431c0d53f140233af5feaaed
- request
- f1783585d2b2d3ad7ee4966d86a325a6e01911c550f0c7d8c99a9ac259059d9f
- transaction
- 472c0824fdb3145da100f0319c9f0be3dac11f0ee61d2a636a7adb6f9b6452b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16220
the chainentry 16220
- sealed to the entry before
- d8b6df71e597ec4b385093ea36a6a7bb9e1c8046a19bc37e8c83171740c100e3
- this leaf
- 90b1718ff662773404a424071f0c02999394a5f1712bf87d08406dd440bd11e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6kSbh55RLG4+P+1q66jlJ1jUx1e0wSRdEa/KzO38GoeRxM1XdxKzEy+WG96ZMZMeVapfni5JXPjrKsoUaTv6CA==