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
- 367e9c6d9c2d0860e541186d6f29682d412af2527f934118c9656346014a8298
- request
- 89efbff3e063a8dc2caefa99ce085097754ae3e841f52a755ade0786200d6380
- transaction
- 9591dcf0ce1c8c0f4683c969a83182af4758cb111d232301626642b195bd93e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6280
the chainentry 6280
- sealed to the entry before
- 59ba8a475571381d045cd5c1635953819f24a1ff223c9ae454d38a9a769b9a19
- this leaf
- 234c711ce3ca59a4468f2022fbb63f096e6133279e2311eea3362cdccc97afd9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XotGbIrv8AOtRVkUlaf6mxSd7O6qaxIe8N8696RyhPRSIlRMRdbn4L5yHxwwkfQ42UcNGsFKRZ/jDPGT6PeaBA==