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
- 95eb9e32ee0fdc92a5bbdd6b63d6d8d4a712f12423405423fed9e59b2f27e0f3
- request
- bd100249682836eb94398b4f4fff4170453afbc9df3fa14c1865d78711d818e1
- transaction
- de55d5aa3c371b371a0024bc19f91edf6e51f9de90cc5306e4c2d53a4b2a3aa2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52291
the chainentry 52291
- sealed to the entry before
- fd1d8045d1b3a6abe1060f5bc84404d8e9c28e850233ff8057623ff73147606d
- this leaf
- 97fe0e07a6da5396eba04259f0d34f6ccfa5d99f9b58915dcad2d583ddbbba3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ph/f2W2rEBSAxNFVfhhzgGzeNFnQVESs/3FwanGMAzydtsM09jNnaOeQcwQmYdLcbwVul1IZ0l6MVv12ZCeWDA==