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
- b3799dec61389e8d20f418fdff812fab1c770f2c61c070fdd26ae36c8d0bef6c
- request
- e55c3ad56faf532589bdb6182de1d926607a13308a20fdbfac6570ac68962046
- transaction
- 8d91c6b19d79a140e3ef5ab613d8dd0fee9bb4461fa9aa665cc1af35dfea3ae4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43828
the chainentry 43828
- sealed to the entry before
- 2f1b45f4e8bb59a17c8ffb9ab607870bb5ba9582d627ceefe5a07ac574bca637
- this leaf
- f1fb9c3ffd29b4dcac5d61a6720f388b3098fb90c4affa1fc56ef6caef3d22d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bIRzx9tHe8BpTSxOjZOaMwYIJEOFo0K2IHARU8rrqQxJYU4PmdFlVzlbnlupt3THKnZ+AyE1zeigjtCOus0uBA==