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
- cb9ce5e48d1fd6afeb9369ec5f0f9411a355f89286868d4f9493e2f2c2ce7101
- request
- 8c4b2855cdb3b3a6f13aa832ec7223fe41a0c42a9703c3b2d1dfef4d580ebe67
- transaction
- e5512b177fb9b5405e97534841f53683eca03f9aa133185b38a344d6b754952ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24123
the chainentry 24123
- sealed to the entry before
- 09b9393cd1d9a6a35e7f05dd6cea25cf73e0c8974fd1a3e9693725cbe62d3eed
- this leaf
- abfea7929915f1218860e532894e4f28e3f71cd4e7f72696e0d64700251c3ea0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eXLngOI0jcYBQTm2FaaZ2nt/fL/z1bFOMlj51a0zAnXpsTO3qOwRJ0qJ2nd5Gt72e9e1HtwDB5IRppoPv6QZAw==