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
- 40135ff3c1c4c57706bdb2f9d36947f174d8c5f07999e58ce2e710b533994d5b
- request
- 526481e4a810a37ee0c5d375e68baf197383197ae8aa3a045d3ea2542f29a74c
- transaction
- 236fb453f3c01e0f074569c79ee53ff3f0c9010f94f08077a28a530608b316f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9456
the chainentry 9456
- sealed to the entry before
- bc3de3cd4ea9e9dca96de9aaab955cd8c4d5baab02880f2b9d9b297df8f1a0ca
- this leaf
- 384e203571359d9a1406f884827a493752c989fd5289fc838db58c20fe2e738a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ExeIuD4MwMzBs35TMhRccRTKDsiDlfEjAtCgZ+hV2fjf9ZxgXB+CdKhidBSQku0Br3ZMMM9W3hkyBSF/CygqBQ==