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
- eb8969ac45e80d284373ef36fc1feef6048dae65d017fab780055e93a323c592
- request
- 902c5cb2bd2d01f73a82121a6a5cfec8f63bec8b3f3b9948a27f36ab6fbb5027
- transaction
- 8838e3798cd72e4dfb40fd8171d918031ca9f0dfb1e75e25fc0a09625bcd35fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42993
the chainentry 42993
- sealed to the entry before
- 640d836e6ec3a1f1df8a4564a6c7c2a56fd861cc00dced42f1b10d6775f0a65a
- this leaf
- de63403314c8320260028f7e817ab3d611b2e911d82fdfff649e3c1c21f5b8b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TWAKUd7eh1E5UHcD64CCe3lKZ+eUabj4t2wvjkmH5bXZEQnTFGDnFKlCjWe6OndXwIYtmXwNeI3Kh2sxkXbADQ==