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
- 26fe5b86efe2405d3649273a21128d0034a9cc6ce32c67bc369c9dd3d6a15ae4
- request
- ff670b77cf2417de597742a44fcf2e81e9985e7bd6dc4d405cd32c7afca349a0
- transaction
- b1b7444461018dab0bdcf204e73004350f3b1e908aa612b7017d993a4dc6de51computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1695
the chainentry 1695
- sealed to the entry before
- c0b520b6dc3d24172b8a693ccfb5e3154a64f61d6febc25cd3845fef76e77436
- this leaf
- 151e925e03920ba10122bbbf533b9122f583923496baf41b241ff69c5ddb8544
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wUot8aKvdohstqEydX7hV94MQeqtMtg+k3ZroGS2EP4j7/pcGaltaV+44Na5v0qG3rfu61H+6YEw11Z4uIOkBw==