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
- b6d84da90c49d9ba6d8baae0ad2a23e63697229010cf399af6f530f9ce87b915
- request
- 07d2984a78d78d32493acfc3cfaaa728906efdc5538930ac03a982d390ba15c5
- transaction
- c673dcecbef533ed8989e2c19cbb6815de008bc83036f7a1697ee730817418e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20772
the chainentry 20772
- sealed to the entry before
- 471bc2143cbc5a983a5e54cc5b245fd352e23c03197504647399e2cdcfb65b4b
- this leaf
- 637916806d26a6432112ea5a1021a83e7fe8d11bc16d84b78c654629b4275572
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- j8yaS9rXkdP4CvAZxMjnlsXvhyXGqkyuFRS+7FzPTGmy1OyZvrIHJkuXbMmxgjBUHJO0oYjFLi21piuAWsKmDg==