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
- e44b34eeb29b04790dea6ce295542db3efd06a6a0f85665c08f364cb25ddc9aa
- request
- 5edd0f5a23ab6219aaecf7a74350e21e25c1c2481d9eef5c19a7355d9965f824
- transaction
- b2d8b088ea601da3fc558b5093d5ec45e78332435caf1ed070ee1070989c1e0acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33157
the chainentry 33157
- sealed to the entry before
- 504a672faf24f1b9aa8da4b21f76c66031032c3f816fd81403a767377b5123e3
- this leaf
- ec3fd861aa96aefc8e496782515cf294d9ac40b0d9872cc6cb108e19012a4b9c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XIAR52G6BBfIxUBJ6qHi+np6r2LbN2pDg07JyEVNXQWFoJXk/VfB0iE5SQ2G7TQsH+2rZ8lQdFen34CV2wEFBQ==