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
- 3eb75f7e62c9a2c56205f503c13708f1e5bdd05055bb2c96239738d58ece9fb4
- request
- a64495cacb28c44725570471172472e549f0ba239e43a2de72047ad6b41a363e
- transaction
- 62f4c2e0b57596d231b13370083fbf8bf66ce4e1d8357eb5b2900caf1fa30bd1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40582
the chainentry 40582
- sealed to the entry before
- 77c4902ee0f60e84ffe641ebe3688c4030ca7acfadd3986b44809cedd4dc55c4
- this leaf
- 0eb6bf69820548b8b6558c58849350d0802e0648268df695fd045ed004aba063
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0f1LoeJmWM8JiawDWZJS2xgFZkvRusXS9ghudxF1tsiNpRvzq5kKjJASMs91mZ+dZLQUUnjVYD6je9aKVstyCg==