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
- b858a8155ec1143aaa390a841afb68c5b449db189c43817e2b9022a976b3304e
- request
- 3c9d31d48484d2417ed3e9e08db5845de3c81cf8dd45690ab7f68ce37da0f838
- transaction
- f76c71d9357625aa4de98712969f4dca8c0e1af5a6c5960411720132d969b176computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39434
the chainentry 39434
- sealed to the entry before
- 0af5e9a45f42f9421d06876926df85d8cf80c0f011a54099693ebe8922a0ffb9
- this leaf
- 2ef136d0e202619bad46ee403973cbf7b8ca9df10f8063bacc233fe77ba75c8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dUio85c4x6yALb1CNF/Dg8b/hVyNtf0G3aGkVJDxxq/HtDUUmw5EzIpwbwM9897e1mkC0XZgE7vF0Z/mcCCEAg==