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
- 401db94b77539e6d843b1c267c4c74eb8e543cbcd59d3d7a6cdf0db3613e2494
- request
- c764d198855fb1f0a74190621f5aa443242a7e735a8863dbd6af98b0a520e93b
- transaction
- fb9c882dac8e2fa79fd1de39f8403586d686d6a8ab7da9da758ba86adf2610accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73986
the chainentry 73986
- sealed to the entry before
- efad63761d37c3c7bf7e0e06e86c7ca794245cb2f1dcb7d163110a78a698575f
- this leaf
- 4e0c65056031afb621784dce5f401e408fb647af8bb92188f5c19c7c9fc75f61
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +p1fL68KDNgGDEvOKqtfM11zfEke8huWnau7QLMMjT4mU1W9uvQZSGWR8rScBcaV32WK4MOsLXZfHyGGA0ifAA==