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
- 20b2755215837949110abbeaf13e0524abd5d38adbe60a9e196f378f4fce4098
- request
- a9c2ef81d0c86222c32899186e0fecb0a018bfd2817bfe1254e6075d6588b4c7
- transaction
- 1d1426973271757c39a9c3c5255661458ce96d2f30df5a05482f20c3cc9354dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28704
the chainentry 28704
- sealed to the entry before
- 1c914327c6de8168a3114aa8b127c2b286a3fac3d2969e267fe3c555accfa9bb
- this leaf
- 6e87746a46f4cf0623c978f84eb92f83a1549b49eb247393447c902fd9ed928d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0mze4Z77t13+bkqLtkS0d51l0hc+uoMvSFRj3ZQyrYtOrYviH+Tl+QNTuHRBo+czH0Qb6arAEpxGQWLZCHN1AA==