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
- 9fa6a794b8f15bdf6b619ac1eb774aaa9051aad531c9048ecd23e00f32d9bb65
- request
- d9be1abdfd0cf789592cb86d73ece1e601a3496d0723c47593f1a2a1b6ae9aaf
- transaction
- d9d0cc370ca7923da4dc1002dfc54b4927a542a17a181a8874dddeaa78beb15ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13014
the chainentry 13014
- sealed to the entry before
- 86a21b0e95cae08679128bd5f7d84ed090db52426d556738cd1b9dcd697b7a47
- this leaf
- 3273bbb2a92ae302c10903305370890b0f890664f087444779014be1caa50957
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YvP46dfKQBwqMhQDovnPfLv0yN/XTlPV4+M9cNdzrosWMeNnjV25qDWWWkkKaIp5IRtMcxVtsPalr0PuSFEtBA==