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
- 203a5ea8d7787394cf5a9ea26604bce735ef766f050c063f1b6befdd92794b02
- request
- 0ba2c2922e1f9695b00d7011cd69277149ef71e2b9373d16a8df6b0ea5e107e6
- transaction
- eee02b1085c36da3e42e1a8b9edbaa7ee896cba2d81e7bfd7078a4eebce74436computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68504
the chainentry 68504
- sealed to the entry before
- cb03bd2c4472fd1bf1fafe73c7e7e1dbed428faa0a358ef60bc8370383e672b9
- this leaf
- b34c7784460ce593179bb41ef9edd5b9e1ac431a4c82e27cfb43d1ffba5c1089
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ehUog3YOr6UlDmSLCOxbxrGoAMUyqR1tWFIN5obQmStGhOgQrjJtd9pxPmgSmTs7qt5Sl6OvF/C3eSetsucaBA==