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
- 52884dd422b19ffbdfb6f8640476a61d1498dafed93aee95f53c37b755c14f0c
- request
- c66ec810171206754ad027891c7065069485a1a72257f7e2d785957d64d2841f
- transaction
- f13c2375d73cc5742c78f2fed62b4514e90e644caabe9052335ce1544f4bb316computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24811
the chainentry 24811
- sealed to the entry before
- a0da6645ff2057cc8b8720c33a3483c6c3d6652ede402ee9a5a0f792fc64ab88
- this leaf
- e16f1f632f1252c6f575be6ec988840dfe006328c28a72ec676bc4b19bf68d00
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JX6ni5PJ/ZKqa56QmCb2HM09I6/jeDBMde36i0y3vVlg1OENj21C4TIxhFt0Nrtjnlght92xOG7tJewZQhJNBA==