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
- 9f7cd4d68a1433c7bff05a1773e43d6fd4c4ff1f6d08352208db5479ce23c1c1
- request
- edff7a9a71abe45d5a63fd0c4fd3cff88cb4efc53fc637d1af30e8abfec56ddd
- transaction
- d08c7dbc854760fb247e660dbb03072bcd62ba60ebcd70502fc59685938bff0bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65832
the chainentry 65832
- sealed to the entry before
- efe47852ce8363c98a2fc807e43f0292070e68abcbbe3820652ab096dde0c75e
- this leaf
- f616c113a736d020bbfb909a44b2ee7227b3f2220514711e97648fdfbfe097a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- //F4ai4K51cEK+mal22Y7g80QLbQ6hBrvTLfYTFbJqm6KE0Ns0r5e5z/jP6NJIvalOmOMpNuR0I6M9OnKDOJCA==