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
- 6e17f8f5e1db3a025adc4b566c9c83b9966646e8803b5085548552de8330bddf
- request
- b3e80a104723ed64b09a98e24aedecee22a589add09ada630750da354f6f974b
- transaction
- 8cc73c4f25e06a10b592395253016f2dd363a2260ba01d271d5ed8e39a83c1d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52672
the chainentry 52672
- sealed to the entry before
- a4bfb8f1230bfbdbcb80da85f35ae6d2cf5a12a0e542aa5f185c5290b70fbb5b
- this leaf
- 512f991f54b1ef29e208e9e5e60bd98c31779c4efbcfd254411c96a1da61f349
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PPw2P+PVOO1hL/Ppwgsu2mVjuKagBRJx3ptGLlwgMjMlANqqXVbIRDfNx21nZDe8bIbT6p7aSqLPL9795rDKAA==