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
- 1bf5e39eabad8dff2aeb2d11f1e05e5572988047e9db351d84ed45042f8ddadb
- request
- 6ade93bdc61889f6fe761c1434a7f1ef80cd0cbff42affd35ac1f62f10a01f98
- transaction
- e5c14f8b6668c90b039f65336556181feb3a529bcc28c5dee3196e779319b0f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12774
the chainentry 12774
- sealed to the entry before
- 4dbd27716208f316959c60411a9ab93d437d87109320fe6e246ba69de3837eab
- this leaf
- ae111b261895c71691a82c0d328932a5bd68ff4d12cd23564bbb42b80008ab20
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XK2/46C/7nzS7NmStHgzpNRe5pU3CHEXs8g0dfvtiGhVm4fQQvM/qSustf24lP28somNwjzlFmjviQupGNIMDw==