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
- d787cda2490097cdab2f6e0499c08d66201491f9060d367bcb51a0a9748fb11f
- request
- 579d1e7a723a87c307db295fb5def8150c9a5ad5c6d665eea7b57d8c16a10bb6
- transaction
- 70e583c76ab1be38b6f4f44ea0228ddd04198493918e9bdf509883f6aa20be20computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36330
the chainentry 36330
- sealed to the entry before
- 2fb93696113b55ab7bf140ee265a1a7ea1dbbb3f2fa64acb062bb151b54ca83f
- this leaf
- ce636b08d9d8306edb41ae20988d87ad39f09dcf7b9347a28f24e2a00f14d0dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BAu05LN8Loa6HNinEkyLW7kz5V4vm3dLvRFYSzbVbyCeookx/uDccOjmcGMjfBwHqeOnAUYaB1EdIieh+CnZAw==