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
- 96c6b24521a82f95ec479cd60ffe62a21f8d5e30442502faa91cfe74e0ec25a9
- request
- d015f436fe37a100aa5c51b066ea542e0ad19da3f6791581c497bae0017633d5
- transaction
- 8e499d99a84c0629f4871d75e652ea3382c449a571d3c5fa381ce771775fce7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4918
the chainentry 4918
- sealed to the entry before
- a8f4ba5e784bc9c5a8d8fd2273a3ae424cb44ea1eed926df8e9441803e9375a0
- this leaf
- 8c646ea42a02ecad188923aac49a6291f32adf6b58649163ca2a05d61e8ac3ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f4Z5hhjXlbj/1X3iwolM8jvYxwG9TTcQgBvOZ39fEYHNWaX75fIJc5Plip4o/OuxYMmm3FkXxoe0FFSuYH67Ag==