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
- 9ccddc8e925649410919606224cd81ea0ecaabfd8cc8580101334204fbc122b0
- request
- 9f88bf4c6560355ddd96c9b58cbe11ec63da3fa22ad04dff312e3a8f36550741
- transaction
- f31fe2412d3317f49d810ed4440e145178ebc9ebe617b0cf3cbef1d703e786facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52112
the chainentry 52112
- sealed to the entry before
- 42846fe895d5beff4e0e8081029371a95be90ebb7f929ae6f8ddfe723a070f74
- this leaf
- 3624b8b7e1b5a81f841efc4e54e62dbb9555c3a6d7c925537c8724dd2500f8aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GYtfg5hk+vO7o/ZkAxyWxaOEXB9lhShGm8W86uHxaAA7E4guZlDnv3K2V0f8oSCwrGUviU6FgItY3JQqBC45Ag==