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
- b55e0ffc05911a9e150017bd7330f497a6c50d06991aeff03dacaf35452d5ccd
- request
- a352b6876d96757f642bde62454449928afb49f56795226fa61ec539353e3e27
- transaction
- 4fbefd49498f60eac762987e3f78a855484354545888cf0ebf906cff2c8da826computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35828
the chainentry 35828
- sealed to the entry before
- 7a2654ccd8e48b1fcb8414580547c93114a7d3a8ec964570debff0e450b40baf
- this leaf
- 74b83e1b1cf0895f85b1aef21d7f70f0acefb98198ba26127c987edea94360e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EdsITB52A4mFmEwCRuWGqxHZN8CCWEGQisHzLvSpd/3dJk15y89WR4ZqtozDqBQvFzUOFMtZ5xeT6YX34LMQCw==