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
- 0fe2f5d33bf84c8cc4461a09af5dbfb99b2fba581270995c7bc14fb2237e2c1e
- request
- c04dd4ccb5648eeb28e3ddbc36af5cb54c1ef0d1399d988d4426ca5d5bd9d143
- transaction
- 94d65e7ab754635a3d2489e07c572a01d7ce74dbfba3ba1173993c100a0b4b82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69844
the chainentry 69844
- sealed to the entry before
- 4e2bef7fd957877cd1133384ff673f655dcd86ffce762475ed716bb2efb19423
- this leaf
- a747f1971ee90394796108f58334a8450a144a03103481a77b448fea4720eb58
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F6UMVFPbrZ7lD8iruRHVVn9d0KvCdKv4BsESZBrBHHDCCZ6zKIAlHwRzoseIQ7oCO9MWwIqivIZUlqBBJ4O4BQ==