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
- b633c73be11e546cd72751d838b5b65ac0e0db8e59d539f35e2f7c08620d731d
- request
- cadf99c1ecd30ef679cbfff1a7820d672c2951e9508b7af9d750c0e9dcb49212
- transaction
- 160853e683ffb4cd496e635de02a13a62e4ae9c140b85cc511326ee06536e686computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17945
the chainentry 17945
- sealed to the entry before
- 7f398c1797733d310c06151bbab2570c6786e163cf3529e0fd0e74c0263e6373
- this leaf
- 0cd158bd31a2ae43f860dda4af955f58aeb592222402ad1c3659c037cfe6d080
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cyJ5Qbfj7xupJHiWMkQbyjA8KNdkRflJrWNu9ewBgFNarUpiXL4nNN86sSutQxeqywzw0uFwl1natEC5u4f9Dw==