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
- 27c9925211dd905d230accae34e497323642e333e6ffd4a9419a02b5c49cd37d
- request
- 44051458c5f863cf0ffe75e670ca56888608eb9cd63f53b7690d2f5492a7540c
- transaction
- e3c98e67e25736df2cdd1b301adefb4d462cfc4a050c9a5dd0c01d2aeba9ca3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50140
the chainentry 50140
- sealed to the entry before
- 97538943d9fb8e4db1bc0f3e2cf761203e0c5f00dfba87a6de6e37bb9743f3d4
- this leaf
- cc9b770d36081bc72c69e745eb048d9cffcb64cf8a83a9263a05718a5ad9789c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WJ86Q9K8h+4Nbex9G15AzehCE6PsfmwiWBnoLFcLWfBZZRRVZ+NDQqjV7Kg9HfM8fHOfhayPVpuDzxUMPx8hBQ==