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
- 781c9aa9dbf1cc21be3735c8a643de023c2ed6b88f9490288fe3ab641aa390d9
- request
- 911c6a6feb3098b1a3f206a981f02900fda48b839409e36157fa285fff32fa48
- transaction
- b748eb9988d6c671be273d5c2cd9adf6afd40f7561a953faa89f4aa2777950ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36073
the chainentry 36073
- sealed to the entry before
- b14d33df7a976e7c3b2ba3cddb4d1811f614adddc83186002abd8c10ca823074
- this leaf
- c33e21df230ad3d80a31727e47cc294e17e0d43a862ee14839e71b926e24a046
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HbKmkAPSMrmyN2rJg+Ou7qZ8XEkYjCMt5yFFf+svBEwl6eHL6qMc90cpJ0O0Yt8xf7VQ+n0TmPg20EBlouZIAA==