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
- 7a4e6d163e84ce73559e1d827316b42c858fe1fe818afff550cc1f491f96eb62
- request
- e6119774eef089a0155f599a74b1cb22d362cb127ecc5f6493121cc6d799709a
- transaction
- c28399b5123c821a212a24389cf3df9db11ad7b7d79c4b1e0893b88c424abcf4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1660
the chainentry 1660
- sealed to the entry before
- 0efd8462318695eaf9089b89b90d729a63f240639a7474d6186eebf1e9ff1bc5
- this leaf
- a137d8dbad833952d1408f4730e0613bd518ba9c7867c6250da5c3991d8f0342
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 73R2N93CRkHJxGf2H6oU7nm5CObOPzsXvF/CRZW+D8MAcjpqR7K4k/YHG7MkjW9amDiAKmRkDfFPl30bwxdXCg==