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
- 4f979a8777379022c4383aa69875826b22d1a7bccfa320cee063daa2413d20fd
- request
- 6833cb86648799fbc0f70923be38c152b759a2bb0434cfc91e85a825249b03e6
- transaction
- 9ab2b4c7b4e94c6588983f580fb0f366b525ca737b6e4d3a502aba2fbb5c393ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12420
the chainentry 12420
- sealed to the entry before
- ccfc2d1a7c3286c2e23e11c5e64f1ae05fb0e0924aa07edfbde44e01a979a037
- this leaf
- e27d723c861ddc85ca67c996144544d72635df9760a55489a1b94a45efc48992
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CIxfCKLWKD7arFOngIhrU18cphEIweEALMZoueHaOtCU+9Z/2jd6Y//PA47kc1XbqdSYPCH/ufxRGt93U0kGDQ==