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
- d786d38dc24bb324363fb15fee23a419af3264d19b6536013205ced1d74bedbb
- request
- 4905bc271c3704f57d433ad334c1d149ea799cbc4c74513cc63cc5a7b1f5948e
- transaction
- 05e26a3184f551dc68368ec1927bfae3215d2930b2fef70827bdae259a67dee9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31137
the chainentry 31137
- sealed to the entry before
- e3bd9c0cb081724c5e1874db5183a1f9ddcdff2ea51ef0cb9b7586d12d0ebf7c
- this leaf
- 06a61d8bad47e254d1f37e6d14ce3d8f1c345c3e4f1db2dfa7c4c91061f5bd22
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9W+ghN0PKojt535MNT9jyAoiWt8VTR+xiBN7PzjM41n9Os9Z7EyN90KAXdYxSIO4uC6dfOH9NLeOq9tPh8fvDw==