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
- 84ccc9386a6ce2d3e70677d3ecd0a601611ef6bb5d3a5a2675267adb0bcc9115
- request
- 991fd09d9860e8eb29d31fe516be9345fd2625540bb7f8f38b98e55c80b436aa
- transaction
- 0cdf86387bd7bedb1bcabd742c00077ab07be4e5b3a1fcce727b59c79872cb62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5502
the chainentry 5502
- sealed to the entry before
- 56a7f7f74828c7a5d1e87fb83946d12a4d4c549ba2f17af264edbfd0d8e14da8
- this leaf
- 6519df03f13807e54ef934f425b96285004ce0b4527db3fb94cccf0c49e3cb9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ElfxGCkvBecMtIzPmH+e4SZ2GwD0eRcBtzkUngh4cqFsp8KrXyYqbCP9b2Q8hywPVvXm+mshSTzRhDKCUI2pDg==