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
- f1c052840c5f5cad548e3e4c6759728a79c8a5d0870ecb6f6bb494cd549c0809
- request
- c7030c330193a576f7691b7795bf333c40d7c4709df0ec95bae1e23943b6afb8
- transaction
- 94a1b1b9d2f8c509408bcc698942efd4936a5b244910179a89159888144b869acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 286
the chainentry 286
- sealed to the entry before
- 6e945dd8d3d4eb4d8f1211290d7930ac668d30b5874662c42f583e6a7ed2f8d1
- this leaf
- 82871d0529db4aa20f2fff379722ee0abc31f4a389c9d9819d80129d4f29b674
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qGK3W9Ny7nIkqq1biBtDM4DaraXN93jS6CZwZQXSx71KMGJi+g4s33D8kzlS0JtR8oAkDuj8+Toi0C2GoQBzAQ==