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
- ee1c73abc508780d6641e3d6a6771925ba93ed8b1c929318a1f57c029b1d50ef
- request
- 1f413c77926184d72cc5a78d2dd290afef75b08e057819eca3893875381f564f
- transaction
- 0d42a51ccdf425c7fae21b407c65f4f133a2ef8cc9b33e4093a3fa959de595eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10658
the chainentry 10658
- sealed to the entry before
- 812e1309d89136ceee99715e4a2365037d7f7b798e2fd8866b21c1a7b537a3eb
- this leaf
- 591e810bbced0947da49ffb064b4103f62f58e07138b57ee7d2364be387173fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ILh1f68Dx34epYvVfyiDxKPN+kGW/Ump0xeA6iEkPiq6NpFu3gakeZA6UOs3tovNSTlk5xgqCkSxbA4bgUrtCA==