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
- 503d3ea4c43700a0627d01eef06ee55f433b8558751aee3fab734db64216f300
- request
- 3c00ded2516bad6b94363a136eed3e9879cf4e637629f109f72fb7d1013d1b23
- transaction
- ee0c6aaebd881d586c4cdffc82102ea6d47fed3797cfaaa1dea44661ed169b75computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48650
the chainentry 48650
- sealed to the entry before
- 86f3cb99b79d934a408a6138bf1e80c89326e9b198ec9a161b3e7b104d9f2601
- this leaf
- c40bbb8ebfdf65db301d865a294fcc1d16ab17bc142b2ed2ed11ed8d56da45cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zcMFwZiikLipVSVLDWQ3YPmng8nCDja2iwlhaCvYUR1DuXQcXMtcvKTcZQYbUS3jCUOD/xBZZGiF8PY1+nboBQ==