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
- ad07d30d32e48330823c406fee471f4ea64c6c60f0b6546bb2bcedbd3f5a008e
- request
- 0a63f715baa0f0e55150ebd4918f8fb0680daaceebba2887e24bac64604edb24
- transaction
- 797238e68edd3d0d4c51e52d2ef7cd4bf2ff2da12cd8599ebd61b01c786cc3cbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25042
the chainentry 25042
- sealed to the entry before
- 3d1b972041f6e41aae481758ee3f000cfdd50f5b941eb83dcbc0bcb7e5595284
- this leaf
- cacf5d811e9bb8facf88cc0307c566a4db4393bb58294cec3e7eca59106e927d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TE9sr3sYSRate6F/uxqCVvwACTdR1snv+L1slL1asqnZkLCSM8odpAFrP7j8VrqOjX8LpSegh2KR0yyVr0VJDg==