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
- 552825d187539f92d101436b44a7dde0d8a47469888c759b4f51e4753a00ba69
- request
- e2b5d1dd4cf8699cf7cc1deab8f97aa64597c0544ba2d19cd907e394d7239423
- transaction
- 43dc5a5fa79627156512610cc0af191d94ffc91cf2d3fb9582b18abb7cb97d68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65045
the chainentry 65045
- sealed to the entry before
- 49eff1979c2013051f2a4ee159b0b58ac8cb5347123882100c70232e992e10f6
- this leaf
- 874a52b515bec4d212378602d3017833264fe0c5b283f460b0764684a12e68c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B+K/rMii7CVhy62iAGSs7IOZsrXjhEMVlxro3rOKuDaew5QuCZn/Y566My7N1y4ll2m968XoEjOhS/r37tygBQ==