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
- c4410806dda0ab8333e5385ff4cd22e4116a375c1cd9e4e2b6698dff167fa802
- request
- 2992db0c7dad3d2cb4168904fd274389dd75bc5b357c9ebdad87e4ff851753f8
- transaction
- f7d40457ae88ec3e009319736e3a1f0d69ffe011d89e9c1631fcf185e986367fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2475
the chainentry 2475
- sealed to the entry before
- 398294ce1628690382c4e36c7543c1c7be76a85ecf43cb38de1464472598501c
- this leaf
- 9c2eeab7a02ef4ee94f8ecc837d1143688acea88adf315b5646f6b744e08cbfd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 20AE3bP4bpSIuS+7fww0hh4GOeIBIyDqG9SI1wC1yD1xnl8Bu3FZqMTNQiVlVEz242RuwigOnQV4nyMr7kjTBw==