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
- b0ed373f7a1a514bb596d91a53fc0a27fb23147a865afef8ca77d73172a6aab3
- request
- b57b34bfdd961f89c48018bfb3c5431eba830b08b5e74b1432c792b55aadc5d2
- transaction
- b0aa5a0d12576e7930ccc22975b966be4f6119028f69c7d2be50e6603379bfabcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19290
the chainentry 19290
- sealed to the entry before
- 53279c880735c54043382dbb655b6877b553d8aceffef49370f1459c76f9f267
- this leaf
- d8a98c2a062cecd3390e0128b4cbf61241dd2d2dd9373d7f652658962c0654f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8gT5ZAA79oH4UYEW1R/G38OB26eNroUavlktvwmu/jieZMUirrb48QEN7oPWwrXPQSYaDV1mCMtkasBwXCTEBQ==