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
- cda48e4cb59f41c38a2278996ef6a7c6309dd2198885b803f32d5788c65fbce1
- request
- 4e9e02f354616be3392f2152f1b8253d732de5aae182e38b8b4ee966cec62922
- transaction
- eeb9a22f6e0acee2acf5e7494075966c151fdae2693c97abfb15dcb442d65b23computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32393
the chainentry 32393
- sealed to the entry before
- 34712613feb1cd6c047d91aa9ec74be5c25ab7ac2d96f6906e37ddf10c0be175
- this leaf
- 09fe678466788e3089a920a2f1a4b45cb6847623c80e45c9c265d1db9e920e1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b2e6yH6c3WmGJlPj9ThSp6AK8SyJz+YZFeQEp1zB/WS8jSCI7d14gtnT5Zv1GdAmN9GRXnLzwIyP186osjh8BQ==