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
- 5bce7379765b0549f27d6345950380cd097225b038c121b0640a5078d6e79f82
- request
- 88df7080d054639305d38ac24004ef511da8af9099dce2879062d2279ea91755
- transaction
- fc12b56950d3df3dcdc209313819b1dda298bf30cab5b9a6aa0a106dd498a2fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 646
the chainentry 646
- sealed to the entry before
- f70c1cf12bb28d25fb1e6a183722593ff5e7736aa2c49d6e9a5aa5aadbf9f804
- this leaf
- 3e3e74270882ff9610bea270d7c241ce4b12789a646cc7f1b008663f5baf394d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ywISYziYKg3qwGQtfZUs2KwriVhbfpGY3G8CAlowjgLasHWY+nttYPcjiGyfkCM+z8wicuxlhKDUTl8eDlgGCg==