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
- 9e74fc8beac2c959741a4365aa547085939268878adf00112325b5ab774df740
- request
- ef3f73423886725781754e6a615c805fde0ab7f4387e7dbc31d1056e51bf4f8f
- transaction
- 2a38474bbcba1d7943f864288fa9fbabbe16e6a5cc53ef69cb7f5ba9dde4e83ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55628
the chainentry 55628
- sealed to the entry before
- 206511d0c7e6bd2d5702451bdb6600ef00c5b3519090ad6f3f21125d2aaa06dc
- this leaf
- 5b5004135f91dabcc96b458396a904b7af21b2eec48cfb518cc757184b9c90cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rbjy2QsXx6PSJ34Cx/kxWkFokBl6jwo7Yu4gMRZo7fG10Yz1kiPc2asuF4FGPHyw8TeOBUz4+g/eyrNWuMdkBQ==