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
- 2374efcc5635bb738100dc425b912fbe89fd129301c313ecee69b914f5931832
- request
- e314a144a5ace582b895c3542b7de996f5b2545b06a5ed3eeb8d5e73fd80b661
- transaction
- 57e61517bd0528995b13523a727da02c4864294461299984e2a5371d9089167bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51628
the chainentry 51628
- sealed to the entry before
- 83ddfa79be02c367f01e06965b80581b96c2f4fa48b4c9098c846dd7776e239c
- this leaf
- 83616ec14cbe56ffb4303bf3d769cd18d1506ed7eccd32263703ee077594e189
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Iz+UsTXsDBG4iMMaA6eVAo+D9c/qpyieh8CuGeUeomtfzmZaszYoWJC8OQFB4eBlp1CLPgx5Vkn+z16HoLdPBQ==