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
- af3c3fbc4bbaf37b8c9530db866620a741467fab1b19abd3b1105eed6fb0f519
- request
- d996d9526ade10d68f7331806961f095436a87fc5387b78e42e02a08b08955dc
- transaction
- cca9fb51396b66182c39ca418368ab2b3e1ccdb6771ed49004e019ad74e3ccf2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41805
the chainentry 41805
- sealed to the entry before
- 1fac43348ceb93da8497b39a1c16a63642e4ccc12005624bd5c59015d5ee75a0
- this leaf
- 9f8aba3d1caf27aa2744030c579048e6e13e7a01aa490e270cf383f69f490583
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2nrdYWWO4PP/onfr2YMi5ytroTAnHzIsRj9MSrkpDDb3HUPG7VDmznsY0v5E0nuXMEjA5ILWg/qp1xkZyDc8BQ==