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
- 5997e22dc959be35358ab18b4b303473cc82076fbd0100e6fa338168a16d5167
- request
- c37aca898414016c71e2617727868cec277cdb29359da5d8ce8087126827a479
- transaction
- 53b60a2e69dfc322a8a7ea54dc6874433fc9e7501d377eab93d588c0752c2b5fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24754
the chainentry 24754
- sealed to the entry before
- eff46fd0ba07342f15ba7400645ac94889f494c587a1c0ddc349ab482950a12a
- this leaf
- 74fb99c744a768d77193712f1e1b4fe975764a2a01754a5682d7c51aceecb27a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lA9knwlRKVdMKggULvuUDgMYJy1HOOABNEuv0E2aw98GZHk59mR1iRd7N343SUMALUqPq2JNq9gtcgfwuwHmCA==