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
- 2910d948dedf93baf923a5f7b0f7d4e6594ed83bf984506706469bad20afdab5
- request
- 953a702f8b2dfee8c6e7ed52ba1871a3d85cedfa625a99b90712dcaa8fbd50fd
- transaction
- 477478b6da3b08f19c4ec28d48f3d88c716f462dc49adb685818e957c7acbd83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61258
the chainentry 61258
- sealed to the entry before
- e66778fcfb23bcd10040f0104a4026fe284e8ca424332f9dfbb1b7c4a8ac972d
- this leaf
- 79d13e1dec4788d92c0eea8e64a7f52a35aaa3cf17fba7c20de58760df9b78a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rNh8USlzWklsCxG0NGi/+jallMuNtu123F0xNOxzV3Wsoj/eCMIdtIqTI18Aa4O38IdqWcvZJmRlhGrJD9FmDg==