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
- 0d06c584c77cee3239a3e3072a1ec138fa06025ef128af2f66e7e71d2a3fb054
- request
- 64435d8c0f658ebeaab0b6f40012e7994b6d80abb79f4e97eba3bc7c9795bd90
- transaction
- 8993ff876910517098de6bdb34ea867c738aa8bf8ac24674f79b11ae8d9ca09fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61830
the chainentry 61830
- sealed to the entry before
- d11bf899e4a84a52ffdf123dec71509723566fec81fdf89fd154a1f1b2e13ef7
- this leaf
- 9f0b6b94571f1b0655b8fa02c04c08a9861b618542dc6aa498c57eb4d00d2c14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FelaATwBq6fHv9D7+25yxaLi8sZv6ioS/6cTxPuqpGyGHvlNQ8UhwmS+z9yIjOY+R9uPqHVjf3GF1ezEmzLTBA==