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
- 9e62d63642f4dc78801e1e870dcf8b887a7e6d48335174e73d25358456e5cec0
- request
- b3b2a4e34f53c98130e676d523687cf0ccd0dde9b42cda0609bd94b23e17352f
- transaction
- 41369662910f67462a85a0ece31d8f284aabd704d71cd992238b6fdd532ce2e9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56132
the chainentry 56132
- sealed to the entry before
- 5942a73422f41b6a22b0e0cecc39c61b39f75ddea06c02d89545dc80897b9891
- this leaf
- 7aca79e77848e7deb86ef82d75c685acdab87332dc21cbfddcc376b6f3ce023c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /pkokHnUi5NnI78diIT29e7LDtuLvm7JOtUE6iqfJUK4lk23VDp5RQXJVh+W/vaRTdUUIFb669egCyAf4EWUDw==