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
- a9f3f635efc4c50f6d445ecd343410801c090962f6a054594457f26b2e186329
- request
- 6882657d1fae74cec4b0756a381f13c7de159865918d2476de9796b01dae8312
- transaction
- 07308a0f91bd97bbe3492f85b3facbc189858f7d387ba8e9a266d6071362f25dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19158
the chainentry 19158
- sealed to the entry before
- 0795bda54b308944cb4c52f42a5bd54f67c4a88285c519e9e4ec8aca2c9adcaf
- this leaf
- c2dbd6ba910a74d9dc2c48363183203e70e261894cd21c2b4d8b3d783f778d9d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IIfiazT4KlJYy4NyYHac+2jzPrSh3Jlic9/L1HQSAT2XjVl3ufmo7yV8czn5IbW4f25Fo1X4VfEZpXygMuJ5Bw==