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
- 78f0a02f498a9800bfd6a7a46b84989782043d6e23dd59361d8445b83eb26af4
- request
- e2c2a02bafa06fe28a9e1f23114aeb4cfc3b915802eeea854736db4641651d1f
- transaction
- 590c80a1a8898ed8a96df797b04c84aaa1e1a7d9e365861b318db3c12cdb1b40computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30549
the chainentry 30549
- sealed to the entry before
- 1f6c29f6a671631392562c58e056b8c19d930d58aad7992915eafc3c06bfee87
- this leaf
- 8a6e911704e8ff6b873d2366376cd0a605e15ba749a1ff96cbc0e785aa727084
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ez0T2et7TqgwGn/qZzyTRGk+REMSFL/ZL8lTVx5vN8m4K6m6HKombA04qjhflIZ0T8KGVU4q/ieC1MxJ8kxFBw==