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
- b48167f9c5ddf49443ac2a7c067ab292520fdade7709d1aba687b02b258c45bd
- request
- bc95f8fa54c2263ec136bc33da2fce8eac80f58d22da6f2751b4f878274f3d44
- transaction
- d8ccf2bcb4590a7d34bf1031d8746495dafc1e74c1e920fe464af96a04a2b580computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10402
the chainentry 10402
- sealed to the entry before
- 18f802fc1c289c4e232e9ca8c033511ce94d4d74b487f8e7e40984438cdf89fa
- this leaf
- f8e7cc0757584fa133f1abdd99f4e315ace02ed0be32de05133e14b8387cb8bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WP6ULJQgGHHRdFTuPTWEYXF7/dhhezhkWjwx5f89E7KcwNIcvDo64c/Jr7UOdssg6CJVEj/d0ovzxQPleIu5AQ==