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
- 58ad95c04ddaf0a7041c7a5ff7c7483d104efb8453c952bfeae83364a248c842
- request
- 2f679f38095cae8b9d71bdd42d349fd819ade0c2311dee4170497e420f1522bd
- transaction
- 6e611fb35e58db4aad6e16d8c80dd7dab6edd18d4de71778e06c73615414c662computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2450
the chainentry 2450
- sealed to the entry before
- 0f7a0abb70f81f63a958b9c53c2d7ff0794d91bed2b3e3120643e42a7733d4d6
- this leaf
- 11b7fedf9fe0872e5ed58c9df8261eff4a55008d87c574361e7a713bb0d2f626
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RlBtOOJuFJyRSK8++RXg9rR61TUOzy9DmhQdNVb1XMFsqi8U0r9Y63oiJu/C1XqWJivwmwPjnNWs/khEqD+ZBQ==