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
- 6fcbf4fdf95e660d2db5dfd5b2c84aa54c0285e65406e2df63ed3a41c7172495
- request
- a6ec41ca2af54cce86c7e2be9f6c5c6d38be6ccc65591a93761b158f1f280fd2
- transaction
- 7ddd5756a900c98c9f04c6c5530c35f9d74dd4431fbc1f5ac234da6ed1031834computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52640
the chainentry 52640
- sealed to the entry before
- 47a0a73234a466edb051cc134a596356e3acab74ba882ff97780d9ee73683b88
- this leaf
- a0adeb12c3fcbfdab74a5bb62e6b85031188e3bf29eafa27229a1650bdd44986
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- J/jFUIK10QzRKp5SbU8Hi2o/hyd6ofq/iMftfaPHm0BvGjEAnZNnD+WnrBlWz0s6IvFdGFJVcx9gZ3GB0T9HBQ==