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
- 8f913aabeba98ef4b33e76b700b1e031dab237d6522dc9bcbc8547d2d705831f
- request
- 078dc8722c5d455ff33974ba8098127e970b32b479e8b21663d6858eeed530ea
- transaction
- bb0c856b7d23c298b98da0d2419adcda185e20252a149b6288aa7d01c2214911computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5088
the chainentry 5088
- sealed to the entry before
- dcc1aa3f41e0eb5651979c64ef95d5cf06bd90e3af7ed8922e207674a1a26395
- this leaf
- b98ac735ced99d4d5e141cc97604e6b353eee793091143c4d2b94999ff024a57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M3Uy9BLHlgi/OsCwF9ZaT2fnQDBRpcrXY+Gs1pGjrlK+WGJbxLXEPasvxgmv6mBWom4QHVHpBKcA7KvrPruDAA==