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
- 3fecd6b60ec0191394bbe631df83e61cdbe7d9afbaed32c1c9d8b52ac429dd40
- request
- 8cf7274152e70c515891c218594c3f3f08d66cf07d036c5b69ff3af96e187143
- transaction
- a211cfe4603b8ad364bbe64d7486092d03d4d0a49b4da645aa842a4fd8f246a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29159
the chainentry 29159
- sealed to the entry before
- a0a0787322d270442c1dbd6a36cbc9c470993a10c5aa6787e032ab7a95d94d52
- this leaf
- 751f536d5ce55e63c63a81b2dd106f47fa7ad3f2b99ebca256af4d19184e8ea0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EkNhpQSe6hJLzCJowNEmML9mmH8kDNVTqHSdgDOsP01mbDeJZRT5GIMJ8TyeNHfa8gxzc3z5mQku5YzAtBvkCw==