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
- b2279939bec525be5d598dfb745d2d8973d7bb38114d8f1ce08516ba71f5a207
- request
- 87bfae0c41b7c5d83be13177ab9598eb95341850048adf87a8833724c7529269
- transaction
- 96ce230b6776a4f5853345e96f6de2076f4c3d9b2ca6b71f6ab7b51208481a56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21110
the chainentry 21110
- sealed to the entry before
- 56e6e0560703eb52cd8091ead0787255fd368d94ea6af1f9db2eec16d4f9fa7a
- this leaf
- e34615f96d5e5ea52fbd32fd40d0130192716844064fe668ed25878de4c3057c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ru7xBBbPwHDX5m52KWq1+46dmqixWf2AfKc7k3QSdV5V1Bxro+lWoizza0gz1/JZVsXK1/+5X9wMK1DDz5dSBg==