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
- 79e9816ce1b42bee922733d8a56f388daa14cd36a2f4024a482a9612ab86af63
- request
- 9fdf5b35379ceb941fdc24a5a2ad69be3e2ce413dede8f9c31b7457473fd7261
- transaction
- 2d3fe4980c5eefebf8ae0848806f5090de46e2d752c87b808621f74b42072bb6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58035
the chainentry 58035
- sealed to the entry before
- db4b1ce9386cb5312db1a057ea07a373c3e911bf3901fdfcd2fdc799accf38c9
- this leaf
- 8285691a455538746ab439950d1871b79bd0f78ee4667a18c0b68e469ca44feb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dHakZnOJghCSEVkGITu8H5WDwLQ/3oEdzPAY19LmduKRMWx0NEAjZ5cagI7C9Mu2GdFSLZjqm5uEL3R84dJTBg==