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
- e0e93fde300becd950c9d9a233d71b0dc3137b7bffee1acdbc2926d8dae03a3b
- request
- dd1217bf00f7bac270c7fe27b42cb40e442ed463e4d3dcc3d7a339aa29c42cac
- transaction
- 796649f57a79313888ca574e4edcf486a1f6c76eb23de948a06aa8c1a19195eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2425
the chainentry 2425
- sealed to the entry before
- d539cf3021d37e1b20375edcba6d9b5af63c95efe53b645363d08999e34e1689
- this leaf
- 4f7f278a9af13df5235d9ead488cb349de5ad6af56967b4f1d1f2033b1344f2a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- j+Sp1EGNmF0P+ADdzbmba0D6vpNLa5tGdbpMGLltMZYjKAjIxs1/S29IN8Gy2JjwxgLHWqZXy/L7/d9+wYsKAA==