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
- a67db963ba48866ebed2c4d2526877951e4a1d98978d9f101ae0d649612966ea
- request
- 7997eb992ecdacfce4e3906c582b0cfe1e9f165498b3606c3db96d54e68d6143
- transaction
- b1f4f684d5bb61b2d9ebceb0e1e5853996eec10064990a58c80cf924ccf88f17computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65269
the chainentry 65269
- sealed to the entry before
- d2035e58ceff1a5a1ceafdf88171a0379eb5df470aaaf682bbd09be966490067
- this leaf
- dfd554552a9b14f0157f29d1df5e38597b0dad11c1c7e5055f97800fd4e11810
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aoqOp8OPyHydNnRaBdubRhg4gJeZg6/zFoQPwyzucj7cyjrdZldBpukhNEeGuQdU9r8RHKNbs47zTX+h9WZECQ==