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
- f9ae2796669cbd7ecb1fc4f61b39ae68c7d264db3d9080135374b94a853f1d72
- request
- db6b718125c17c300aafe03ad34aef3db304138861a07ebc03033e774883a200
- transaction
- 50803522b5fff19eaf546f79df05cb2bce9e091c930faf65e05f260172a5da76computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 736
the chainentry 736
- sealed to the entry before
- 59e0341e8afcc2c694b6557cc1059725bc02db47cad8fa4dd85908b80b593f8b
- this leaf
- 79c8a0b7a4ed331a3d23e0ce1b7f29522f848e1f11b6d8ed5fd1957c19b141ba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ork9RQ08WrqiwxFOP0VrQpR3mwGI4XFlmzUNv4BqYs+he7RQulqeCoMI0GPDU2bHvR008m6qZ7jPTJcqzCH4BQ==