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
- 106797a2b781733f39ee0e0ec2ea62be5d602ad3010e5093a27a7bfa740a26fe
- request
- 8aef15f48cf3235f1d67a08846082fdd26d7f887f3614770d415ca54b6fd6d5e
- transaction
- b23290fbf9cbb7595dcb6b3f6dd42502426b53d84eb5b82a646679d9e6939fb7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38064
the chainentry 38064
- sealed to the entry before
- ae27f20ae257c13b92075b3f81601250e2775f7ba4561efe11c6c3f7395aa760
- this leaf
- 9f4f194615effb0986ee559d55cf5928e0416f7bcb8c67c33ac34f10df8be5dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u+dA87SGnfMzZx/cc8d3kQSkusMBWY2MocbitMPtrIHxKgL8l354JyVRkOjx1WGwVyE96GUxIppK70orMcsBDw==