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
- 652e4989d1d1a7cb0b507994a5ad0b4000bfb5404ac121dd7256009385e6ce11
- request
- a09f9582819e1839a6e4cd1f07aa49d9475a3836737328879f400ff1f5c1b4bc
- transaction
- d53cf1b832a205d41135c24a0ea9ab40d97338241f56b57224691278981b47a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18256
the chainentry 18256
- sealed to the entry before
- c4b1b87bdc74f8aa251708649b17d9bca2fff530043337db44a96ce246d9f5f7
- this leaf
- 39722f156a2477dad07eef54095106594992f53c341f0da6485e029ed1a85ead
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VDca7TzCPlfx/gLiQdfisu16MNeuSBVpdu1wsu8R4Hli+3N30kE/qyDkIQw7BiTjFEftPb2WdIYrA6SglAE+BQ==