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
- c2f958901d24abb10e409218ca418195a194a3ca8f3ca315c23e193781a502f7
- request
- 00fceaced7fcfd169438ccda6f1fe3aef0a7ec5495daf662f0d709044aacc349
- transaction
- a15a23060e3957d871b31af0b8d80e9f343c683f0c018c6e53cd89763c4845dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 756
the chainentry 756
- sealed to the entry before
- 011d5999de58d0bed2ca06abf9102fe2832319bd9ced93d066870d86bde5a95e
- this leaf
- e04956135dcfaa730be17e95b269e7cf1eaa55a5bef35553a67570446daaa22e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5wKnOkmoFiZEfxlTW3rhexAb0MCDzzQrkV18736EhxLFCRudAiG+pUJXjs3Dy9aBli9dT3Oi+ZK9Vj27HjVYBw==