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
- 24c3a08ddfb33b564c46e9183c8c999a474ae1c3b5d51233d64f47e6dec3a5ae
- request
- ccbeab687fb1d86a8bba1e6276f62320d61fcb693774b45d34db6bf5f1209e5a
- transaction
- b319b2565ea080d4182be3d75a91de3a419a6eb224c79334b2d75268f759cd29computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69658
the chainentry 69658
- sealed to the entry before
- 99d21a069b9eb6aae6cc9dc1badb9f46b4b1543ce058f62c210280e7a43c603a
- this leaf
- 56b3af67db95ca6a3408743dbaf61ffb3dcf0fc0e6f06398e5a47e273d054847
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bDzg3OYlXPrWANWRcbN9o2v7tlUpyhfem6Gdqh9X8lzRwPf1+E8EQh0kfU4MtnNHOBGauetsCjPsJmlnIXXAAg==