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
- 42b6d88ba84b650c54cfdfb3524ec387ef817ec6b42771ed57490a428dbf12d2
- request
- a13ca4c2f5f5c18c55bd69be447c5dded00556fe32c5cc380698d869b34a2e67
- transaction
- c9ff6e4f62adeac88205fb5215dd8b68bfb2b4402c19907598a543ae4abfe431computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55820
the chainentry 55820
- sealed to the entry before
- 9a13af4f95384344ccb55b98472161b701f80da9be885c456e6c6b6ea2e15628
- this leaf
- 47553f151395564a6837392d49a67281b05cd4d56da559080438ceeefb307449
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4h78Ftap9skU6SPxoP2QD3OKMjS4qZiMKOL2KQeJqUmXhd7bhxSTVgLr0/Cp2CIWhdkg8e8KO2rvWYhtADvfBA==