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
- 9abd25766f9b153ef308146693cc7acde6e27903485b90d0eca4ce0a7de6fed0
- request
- 8d446f73328b12cc0fed5a1351a1aaca370264662ec8e8ce32ffc81bfade8792
- transaction
- f807576af47dc7780268f12ef7fc71b323ef2da0199190373a91dd4d60c1480dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51964
the chainentry 51964
- sealed to the entry before
- 21c33f656e2ae0d0e9533a344728acee7cb6d71beb8487942a9a1fd324bfe349
- this leaf
- 7995edb04adb888d7a3adc238c0b10d5fa559fc3dd9cb7aaa1f9e99a2bff91d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LxijxS+sVazQ18/CafujjW+UsZLvfJVoIa3kJmM3AE4a97ZyRM3u4SRivw/PnbSUozdXLemPvzu5U6c9nZXgDg==