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
- aa834f863c9ae89697e4e64ce4b65f8261dbc6f0b34b131f0638d74319e90d72
- request
- 37d0668701c3e85cd5009843f6feb68715dcb849b08baa1d72303e7d44ef176b
- transaction
- 0ecb6947035cdfde2f15b471b2dd71298ebf790cf263650779594833bc006cbccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23312
the chainentry 23312
- sealed to the entry before
- 88e1b86b984c748805508f42a5f5dcf78cc5b423ede5ade72690743e4e54a600
- this leaf
- d75bffbfbed058dda5d5cfdd078515e1d6809a6f3cbd01849eee9ac934ba50c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6HN+65ceppanebIX/IOTWCKCAz8QC9HXE7l2IxhXIQqasM8hGnqvtuXVq9LCpJw7UZgrlf6En788dqrl7b46CQ==