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
- 3a948c89a05c5c617437d20e9d2d910970b5f8d70c63185f48e525b46b1f381d
- request
- 49c3c34e1800fe975085d5c548cd572bd44888b7cee7d83d3eccb882af405594
- transaction
- 22cf07c7454c246fea070aa4a26efe12238c363bafdb5833b4117fdaa8440412computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17189
the chainentry 17189
- sealed to the entry before
- fdd9689e05a3a8355834ab21a0867c11be74abeb5e13243fe50ff176789d3789
- this leaf
- 2c3638b00a45d626068675a31502dbffc5d79c2984bae2dc58cfe8c1a4c809aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X17fvCDX5K99JT5nHJMohhAnUW3dqCSpSifr2gY7f6kzrP4+g4N3SBq0BC9ACpOt6vqk0tnJoruQT8M3h1cBAw==