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
- 0de9da46bd3970abf9157d0a8aa8667d4dc8fb514cc45b7a5987dcd2b8bb1828
- request
- 2f0a843f879b7e06aa97488c0aa040690e936bfee19dad76504a810556505d79
- transaction
- e7386a106e863db30429f64701c95731de472f65661d786822b1103a74fd4c90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5093
the chainentry 5093
- sealed to the entry before
- ca2ba6bd1bcc50d815c0e9dc257371ca8b6fb8a20f43d291eaf966d69a454db8
- this leaf
- 3ee7af5de5d0cf3e1d65b96820b8c0f60280431b6cdbdb1c2bfe23941e925559
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ooy+k6+PBM5irCWhUXYBiRZvUgWbDxkEyPopec/f3XmxlKJmvC+eWuAdIpWoQqoi3AFSvEQQ7rV3hy1uRuvEDg==