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
- 23183cd8a4f41f750bf549b0492d95de143642c027e2085f4022e1317c189626
- request
- b934e3342b08361c41cef4f3e99963e9e547c06faa9ebd84e296fc6bd881ed0b
- transaction
- 9f83b2c43a976daaf778807537fa9720420451480c04cd4ca9b20c8fc13dd484computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60440
the chainentry 60440
- sealed to the entry before
- e5929136c6e0757dca9b3f87d7c5482ec8178b5374041c96f4a5cb770fe3ab6c
- this leaf
- f64ae9623a0c8bc1155d04b5854f6edac4acea315264b8bc1365efda68f192c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AJC/wTmQ7z+TKWoz1MRPUcL/+vxEyMAO55+7eOtAh3GXaDM4/zZNUYyYWrlEHyFWWBvd2BTHrRDONNnJa9KLAA==