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
- b14bf5df62b65c033fe2af5987520c9b371fcd44e7ec408dfe75879e2f48318c
- request
- c1b1680d25ad4c8b99df72a68701d48f3d48ee614ea8e9d5afeeee78e391f085
- transaction
- 57ec71b8e69126fac602a7ba5acd27eac92de439f28c811b06cbe5b3ddee5a02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1915
the chainentry 1915
- sealed to the entry before
- 2dda1a400a13357813fd31565b4adbe9117869fae6066eaec135844c8127f215
- this leaf
- 18c744d8fca15b4082888a3bd2fbbe2e1f468ec930f72a2649058c0fdfb4590f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3zq+z78Xos55Gyopb7jGgxNdusy7uTxkedR6bPMgBBonvzd2Kn4uevg3T02dv3LsOvGangN9LfyQXMHfp5yGCQ==