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
- 1a6ff44929ef13ed423498153d18b2ec9ff49b212f10bd5411898d91e4dfa5a4
- request
- 9a6aa1395018d44613e746d28f15b4d51220ad9d79e0042176b00fd2991c975f
- transaction
- 112a955ce82cf7dcacfa20c17f189b8cbee8f96ec62b799623c0782396450faacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34403
the chainentry 34403
- sealed to the entry before
- dd9f3500eb4078c74c0000c55302d973fe30e622f727b2862467a1e2c74dfce4
- this leaf
- b72db9687cf595d3f8e58e3fbf65157a7ea5898ce90f85a306e749ab6ae9d18d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9yqD6jUNIRObKDYJNhKh/S2XVQWKPzkZl72oCGE5PkMimAzECO7bS9R22FWnqgT1ZFRF2n+FdSr7uF6NJZ/KBw==