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
- 36123e4586d43f62af584f400e7c2c67f476773a0c5876ebe8eb3cd7976c091f
- request
- 0e33450c5d550d54d77711119b705b69cca7d881f8fd23c6a542e764e381d415
- transaction
- f3584ff7be2e1e512a3b3a079b49165ddf889a992aada7f7c73ca1520e128e21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75828
the chainentry 75828
- sealed to the entry before
- d226d2de010fb31b7d31eb1da9708f6e09e070e562cd4f10109602272a7de995
- this leaf
- 807e0f12ed4c675b3443cb5f76cbf4d617433331d7381503b171e58e01f27960
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- of9/t511fxmROpOqfIKSxT4LWOBNAzWMU1UYBsMjySDbAngYuibvihuSBSgBHizp47/WkIktt6F3N2uY9fWgBg==