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
- 64a3caa91ddf5013fff0c0c2fb522844008bcacec07332f86d3443b7a56dbc35
- request
- ac82c9c735113f5a5a04cd414a6c9f36cca7fa4af73ed587382b816fd783805f
- transaction
- 2f54ce5368993fd51af0b8a1ac8c2042c789b0deb79764cfd8f090b6c5160392computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1645
the chainentry 1645
- sealed to the entry before
- 24415fe69d6a838f0e3df1726fa21a767b001399d2e61abea08822bff7dfacf9
- this leaf
- 61ca4bfc4143592ddd75f680bdad47d72af1282eed2cd579ac0442fa2235ac4d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vmyuQJALBblwAzFNehxXi/Xyd3pRJTHpWgyg/APnn2/oWTDIA1TkuZt7bhGeAN2Mie4jXf/6Uu8mPy8Am/x0Cg==