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
- fa78844671dff39f128e0e5654338abeec81943f84f7e3ca7776aecf90d8cbef
- request
- d04d2018d9ec045e9be620fe207ffb5349c2cae9586f9ab307a3d96d4c6fafda
- transaction
- aca656c92b51f4f67a24ee00d4af453346879fc9b0cc3b080806dffbf68ab48fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22963
the chainentry 22963
- sealed to the entry before
- d3f7590c2c174bf7c708e2cdf6b90e6e8c45e95b1949da55570137dd710d453a
- this leaf
- c65fb962e15ccef68e56825a18d43ffc4e21fed09d8eb23c019673b8c681c7ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ePve35IjofpqBGXZYgBxZlJSDXuk2HROU4OBiRrFfltx5cSWsFMYIfHXHbHc/mSEtrX7ekHtVDD7bBb8iGDHBg==