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
- b66ab5b3d287fe41171a4b475bb46b3e9f781b6e220fe258d0269ceb85f00406
- request
- 5560d93eada6ec719c98e0efe316ad5dc07c90993de5c43b88c7837df6bd49db
- transaction
- ccae1c672f3e7517bd1dc2c8cd08d2192b59e2b46d7263e48bf332b48ba70ab8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56339
the chainentry 56339
- sealed to the entry before
- 8c3f27c36cd39d2c044cdf679ad3e20e9508a369401035377206c1f538208e89
- this leaf
- 6174d48a33e0895d2c2357f4ec233d2dfbfbf8c4fcb0b1ba24364a33b00c9ead
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I/u3OQ1ZClJMwdEGSXz9He9mq3neGUOf1NdGTG7xltKdOxny8DuyLq8gQ7TtEJwQ7Zd1Hbex8cqlijLkWyW0CQ==