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
- 6fd8ca5da612e05afcadcd1f36a928ba3da45e6566c3b3de2e1d3ca076bd4c98
- request
- 6c78f967c8f3473b3a9b4701f7e904a131ac0b4f3ac5868999ab659b984a76cc
- transaction
- 2d7a434c60118fdec34287b31945caee3e2c574c1722768a4a68736bbc246e99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16250
the chainentry 16250
- sealed to the entry before
- 4aa302a830695df00e308e01eeb4aa59d20a9f56917638ebd2a1016ce1691c44
- this leaf
- 029c99600cc7662674c2660a14028d894cc777ffcb47f74601f5c533a7befb87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YLomuXpPPBvcgrItQm9KqSgplpjau6KtPIHO8lqoUNQC+8yvM5vmP+ISV+VlAVvAcIEv61N+XowVcIHEGqCGCw==