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
- d53279465ff20dc7883672bd93da9132018bbf27c44ed73d71778b3e2c410ca4
- request
- 62ea278c59ec7bb636d6a11f3e41d572a27de41323585ffb9b5eca86ad725267
- transaction
- b68fb94a83b543770e79ce9bb22e2873096f28a66eb27156c09d79dec12f5861computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23066
the chainentry 23066
- sealed to the entry before
- 8b8bc51b6b76208759df935afb9dec865be2078c51afd1ed2f98293b38a9ac20
- this leaf
- fdf42a459c275e3484831306b01daae72584ef1eb00507a877cf18bd97ce4ddd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ds5gp6W6qaGzzPwaMJ909rwn/loDYRWQBlt3Z7m71vMWJE185myR7ODQBlvf7L0TKT+NmEHYA15zX68wNHsOCw==