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
- 3c3f4126cfcc8b1d6e322044bac48ce16a27d6148ba5ef5544f3da91299af35d
- request
- f20cb05592b88b790637edd339fdabf298d5bd8c7a98f2e188b61714a595ccbc
- transaction
- e9fa506a69a3f0474980050e393e5cd4c53ba295f748c2cf3f9159842e0fc116computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61654
the chainentry 61654
- sealed to the entry before
- 9193715af8df62d653525da89d45db40a3b573e9c1a1de9ffd90f25659bc1738
- this leaf
- 3f11fb700e98306f0f12f98c580399b7b3b96bf777e86f5b6346d0f5687c8b11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wnJxYtskScWbIEAg7iWjzcAjIgtD0hH233WneFF93yltpYQc0invOXwXM18Do88w/SnRbZhP/CVOzmXEr776Aw==