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
- 5eec6f49508961ce06aaad9137f62e8d04483c79699f473be9bd77c42b6d3c68
- request
- 425008e9da579bb91de18054401a4ab3a78ffe65e86f2d146bcbd4616234c69d
- transaction
- 04c4c2caab902c9a482d1fec81e14896d32d13264c5aa97b81f6c96e3475059acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55040
the chainentry 55040
- sealed to the entry before
- 72d261dc911da22fd24a22c487eddc93f15fba3938d4bfb9f62d927991731d2c
- this leaf
- f5f459332e8a737ec8010b40ff23e2e0cc278b435d2e7f16a0a33367ca9427a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VmU0SJl4J1x7VIH+xnbDH/ik/NtOe6moU58PoPHUMm408Qr1ngTs7AHVdibyx5TFfzU5JUgxNbWDxPqsI0nfAQ==