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
- b6446ff7e313679a354c35dfa028dce654032aa9af1764ef65ba8902d08eb5fc
- request
- 9b48c6fda441efd945efab904019a03f1a032890bb88fe0aa0328ab1d274e9ed
- transaction
- 93e3d8e150d9b3054191d55043be3e2deb54f50e63c3dca760fc1b93f11ad4d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1670
the chainentry 1670
- sealed to the entry before
- 29950e5c41712bc61df153a7baee8c30b31de84ef739544c43aa18ffda9982e0
- this leaf
- f2b4b4256ec78983d87ad7fd40e84de09cf5aab57233d67f380151fe2d70f596
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lr2A8FXRPRB+seDXf/+G6kFddfe/dA4hhI4stoOSqr57euIxntOSgZRLIpj3GIcSihMyqoNeHRnCjuLpdnNlBA==