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
- 1b3ddded54ef98b28c3b74f86394e266606efe05b0710d94459a315b6de11d0f
- request
- acf1c40c78e6f70fa237fd40c299c458df8f64c791da3ec78c9dd0d291b436bc
- transaction
- 512609816da2e751126aba3d2520d315f06b4400ab02200f5b686d8fb3dd4a02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75645
the chainentry 75645
- sealed to the entry before
- 07d836684e682cd001d617b4825df60423f2d93e241202ffbc6212dcc052f7c2
- this leaf
- 38d5e7df54c0f5f3d2f3fe87af15163e3780a4e5861039e7e9bd983edbcf9cfc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VdboRCbh4MYfpbHkF05EfmSHBL5fqECGj21sdrZLtXzztn6DYIC65wZ8ZExRpDUNw3DX6BkhHD4OHVkaRo0HAA==