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
- 73443af2aeba6b2dc45ddf83b4342a82c701d34cff29c510b8e659eccc41b1ee
- request
- 879e06e09b1c35b3e70f9d15f7e35c2d439d50e89a478becba634fda88059093
- transaction
- a06c4f58af26d1d3ee7ce51facf413ee1c5c54f6a56b24de3d710bad764ce80ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6355
the chainentry 6355
- sealed to the entry before
- 304fc3a4a4922ecb2d08566a97fb37e07662c9ef661da6ace6a0142bdbd8c58e
- this leaf
- 1e42043bd786588db150aeb12c6fcf2b61672206e15f878c6f528a1b622a773e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7W/XZBOKLDMc6Ge9z55pmVthrFMjEVDhAhVLO1Gl/Y66/z/myIIGmEKW3AQhxBq0Tz47kRQDSM35DtwHmFGzBg==