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
- 2c86562604aeed9770f28409480c4f03cd7a0ef348e036ce4d9a614c46c93c14
- request
- 265680c498b53168a9580be606ed1937d8134e7f857c632ca103284da5df623a
- transaction
- c93f72ba88836831b56fdf594d88e2670b13eb01c9f8fef6967c6efeb676588bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43028
the chainentry 43028
- sealed to the entry before
- eb86c586417f7187f8f0daece9c87b17b66a4d37092c4302ec450742e650328c
- this leaf
- c4ba74ea0b98bd27a9f556f3e5595792d942a74e54ad7ba8d5b2b7a308d5c552
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ht3D58EtsUV7HW8X2dV14uE8E2wZnbrAqijJRfCVZkSeRcwEgxyBYSURK5N0KkAWwLFNGzFQvNEScbqC/i7CDg==