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
- f3e7319d708f5b36761de156c27efc3f592ffb8713764d911ef36dfb01a21b15
- request
- 6430e642d6553888dcf0e2cc15b278311e75bbc7ebaf22f5f58ff07077be83ed
- transaction
- 3075e372d3847770a272a6cd61497e774875eb096d70e07d0b944cebe64d6d19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11770
the chainentry 11770
- sealed to the entry before
- 22150984f5a9d0a7147160699ec8683bf272d1c46ceceebd2fb01ebe7542fe75
- this leaf
- 0e2286ce480910bd67b7ee9898489920732bfff55466931305542d4c03fb49dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nD24VxmKIzDQSgoEwTlTBM5g5YNkmilN7VGt22+/ssAVK/6R1LKbGWDRAloKUGAnpMrlgdOp0WaJnPdpUUiIBg==