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
- f3a68421068dd00951bab383aa9268c01ef85f62a78608fe18f5cac653e1c04d
- request
- 91d331ee51e60e3184b0aa8627b378d4a324687489fc750e55317c3aab55a5de
- transaction
- 1d33453dfa157123aa3d7d2e7c6fd536ee0c835a5d40db5b3c932dce3b0ec826computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42799
the chainentry 42799
- sealed to the entry before
- c9232dd706eab9c4f4ee53864f7068dad1ff09d785968cea9359dc4c7c51f53a
- this leaf
- fda1597f332c53ef6b9e7078f44abe20642fd030669c7562f3cd4f2bc5cfbdbe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l8J8GU9I/L/PLl5N29nWT7P20+Y92YP/NBSCC7RRqw01fD8MFyQQPE65mliO8njtv8SFntDDuvaxtDvTohaXBw==