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
- fbfd5eceb5ada48e0b4c09074981cb85c4ac859f2ef38847a569acedf6bb9767
- request
- 23756c308c53134f69b9ca564cf5a3608d51299efd0dc49b9fdbc6ca7f63efeb
- transaction
- 700c3b40e4310fc6dcfc963c26b34e65b8ba86cb6310da8010762ff5f333bc3acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21745
the chainentry 21745
- sealed to the entry before
- cb3f1600d87b90d70bb50d0a94ee743dacbada00fe8a2f6abf2f3fffeaa8c931
- this leaf
- 1e782a73cdba4247909134814d246489ef0e4354ff934542341f30801d54f7ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pkZvcHZp4brFDNkp0btrcKB6NGJWDIA34bf2G1pFnDupAIzhYZ3324uEK8N06K2PX9CU9VkHIrx4Cc8Tb34XAA==