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
- 5a669bc314003254c8dc370f82e308383b14a57397e65791a53ad74267341196
- request
- db7625258f42bd856a1ba1461295c59d0835e1050a7ec725aa8bc891634d5448
- transaction
- 709303ac2e0c91ba7e7e454024127c713d88eeb140ebd991f53d67256d9895b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15972
the chainentry 15972
- sealed to the entry before
- 14076ccc76f9098bb0bc7c691252527721d72a13e7d4b93be9d7ef81d0af0b83
- this leaf
- 4386d538b01cad380625114e10e2ac1884bf3e1ee34a1b3a36856e316d5e67fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AQfEq2iUZ050L+GxvWb4+4v8pgziAiLZfoAAnjjq3ARF/d8vslaWcqCB7ued9ncHO+2KpYE+TW/K8rRs+agMCg==