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
- 2accf10f49d22de665c2586347bc382e7cf3976ee3da64c79640542bed37ea60
- request
- 9c5d6d925f65b9f60646b31570431be9fa5f73cea7ee6509ed28123bf079a64e
- transaction
- a7a0793d5f04c70875db06db1edaf746bb6243d574e6218ee02950f1ee0d5b99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54612
the chainentry 54612
- sealed to the entry before
- 43cbfbac28d356dd750f51d99140af36c6b78a91bbff82bece145c8c3bbd7561
- this leaf
- 7061b6717608d072b77af0006a67c57f4db20f77859d201f52c371d5544e08a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zotC/rs+Ov22XTHvNz9SazZgielx7p9J6WEY9+ZeM8b6teiZhCQQXRs3cKUSrPy/i4BvP1jk/Q9qtR8bcDMyDQ==