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
- e9680124ed389a0bd6f8b70d3d82195b1ab8da63cec3efdd3fe1aa7edf0600b9
- request
- d006e928960ba7b400f12c6b056f9751a2529124726de2ca9c23e53678a2302c
- transaction
- 972fa09d220e9938474bbf611958a772855cb2323a2e90c1816c52ac293da433computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29124
the chainentry 29124
- sealed to the entry before
- d87501c55878badd597fb5d45974d50b4e90e2f7c100b524410746f0ba87bc3c
- this leaf
- 7dc6793979fd3bb03b0f2955a8c5ec9ea9ee87e02334e54cee385a503c340b37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TZ1w6+7CUm+N0FEdyaoEl/U12UFssA5LxwKOxrYwm2YzFRHgL4X//t2IF3I5UwDveHYrxyxqoUPPp88H1QFCCw==