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
- 195df5ba9d44019451bd70c14e88d4333cdaa5f2313c50d2c09a51e653166c0b
- request
- 8f2b62b9ac80412f00d6753219e7ae912873dda5f77a67e6543c968963e1e192
- transaction
- 4f51af331bddc8dc0b8725f06887e1a8b1050d6c77a3bd733abe17ba274e7f1fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77740
the chainentry 77740
- sealed to the entry before
- d336733b722d5631cf4c5b35ae95e4adbd9c3669e19f466a6b9760ac5f95c7a5
- this leaf
- 9d8b6d6405dc757391f15b8b0317cbbb239e933414d1ffc5d60799e06907fac9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SMr14ik7iupA3H+f6o4RzhOGzvzX+UNX9YS5xO4jQR3TQxN+SEhE7kSXnFEqCxzU49TC5zupnmtmm+OLDcY5AQ==