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
- 6700c2a1e6da9d9bfdd02b0edc18ac558853fb77c4391c6c63c435bb418efa46
- request
- abee11d54d98a331932cc9f1090a4ffd18f070b6a48f350234d4ab0682b68a78
- transaction
- e9eae48eec71652c860ee9a4f5070d66e3a65a7c471b445f867a7de8c1f114b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66755
the chainentry 66755
- sealed to the entry before
- ff683865f05a7063d248db1cb39a9d5215e725753dc0617d3787e4789cfcd652
- this leaf
- af3d0679e57a287a0bbe2c79d3dca08f8ec78fb8fce2bf186546d25d0d0f7caf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /WZRZdjawGjPU1ZXNyREThITWC3rho89DqVwvtTeL6e+GBeSH0aySqL0gog8qN9DJWy36LiVs8jtewzaJkUgAQ==