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
- cf53f46133db7195a101a405587f13f7dcfebc641468c1824ca591598aeee69a
- request
- a9c9137052bcf647d8832f195adbbf09e7bd11519e9346a2148a4e23d37c039c
- transaction
- 20e061de0c5f9fd922ad87fc5af95d22f3479bec10707588c7f89a2154a288a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43781
the chainentry 43781
- sealed to the entry before
- 6eb9384e4fa1302771eee5db42e846c12deef7fe94208511e642ed5a938f19d2
- this leaf
- f786c6f148703820d17b9b51c96a45a525d638d7b3346eab46c3431abfc0f5d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9EgVWTTiHqL9nJXGKKGz3bcciI8dPbA/hBea1yL3uznniMOPknqlzT84/jR98u6K0BuaiCDuDEIguipCWjO4Aw==