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
- 9fe04646588c4a8ecd0341e4b7c9eda343a74c3883776f5a2d3e6cd982df7cdc
- request
- 839cfdb6c75f224208c239e78a4ab75b179b1bc4969caad0b287bc5ea90b74c0
- transaction
- a7fe8ab44f1a3b37e28155404abf5ab63e6c289db562d4f9c1312f5418b27b02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36077
the chainentry 36077
- sealed to the entry before
- b629278f1d95687dd626945b06d395fe87aae86be73ed74c9695dcdb8c43a5ce
- this leaf
- 8ae8e2ffa6d6b073d3e059f84a415613a0407822d9809173b432949a9a72b801
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 66sWoxrHK8CnAEQFNfGVjFWj50XZneiF+NHcqi6iUPAvXEB24AILKnKmC7HF5ZM8IUaeeRfj+6SErRF5nkzmDQ==