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
- 542e31196e7265a38f3a573852673f67092815bcbe678e4f1ed8ce53e40c25e1
- request
- 3994bac439d4f90a663b06de183f5674188494e31f579620ec509ec5cd16b226
- transaction
- d466e6b64b0054124dd17f971d0927e4177682f77c720b2af1710690a2a6bb10computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52141
the chainentry 52141
- sealed to the entry before
- f483ec2bf7e98e25c648a78efd382e7179b80bf6d31c465ae4e27e930dea5cdf
- this leaf
- ca49b16ac1984a178173b8f6bc6e5d3348a8ab8ad256efdfcbf4ae19b30c5c98
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G2PZ1QORUEYlR3Njc6zCNSeg8ahHbSNJ2lT2X5O+5z5/w+372nCTjbb0B1KT2ZeDDnzgmuw7BLiVsWbIHnPVAA==