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
- fdb06e3fbbfd91efa10d545b8a27542ef9ca80a1132f48ae8129f9bd2f15b52f
- request
- aa5ee39410fa1d0fb4026ee591a0fc71ad23747e54bd69480d31439d3c650529
- transaction
- 01d6ae09af593858e0d6bbe390523b88aeae0b819d5310fafd52f9c9225346a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27773
the chainentry 27773
- sealed to the entry before
- 04163e2fe039c67f32a0fee42b9139cf333b4a3f91d51c5c9913f64ebb8b942f
- this leaf
- 4ebafd46a1a145c87637856405ee0da45f71253b1d9bc88fb58b8ecee1be8e15
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mZiDJFIt0GdUJdlPDnp3w5rMCznlNY2a2jftuYkf2yg7Z5hBRS9JGhqRpuJhm1IEoWS16x8LBOwhLNVU44KSAw==