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
- a5f640ede8d1a4a9c34521e1c69dd09320d19a7cdc48f83cf7e23aef7858b052
- request
- b575ebbd294355f8d6dba894a956c265ebb7eb561361a70880dbb5e494fc510b
- transaction
- 8e4ae75448e0e1e078c13a1651cf404783d40b371af78aa898cb15a6ea7bd144computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4349
the chainentry 4349
- sealed to the entry before
- 24aacc6689a33e06cc9001a36aab66e63fa2fcb1ebe59335205ee28ea9b9d6e7
- this leaf
- 5af9f4c050d86cecc350fd050d35fa0e953ed803be2ebed27d8e269d8d277285
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qQyrUsiJHpP75Tgazg/rVqxT6kQUND+w6NEcge59LJpaQIWGNBzji54Ehp9zhG1/pbdkeGWzklZBniPZXZfdBA==