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
- 51378462c66974c8b0d10578d64df287890232d9ce0a9ea05d5b2c6f37742a65
- request
- 8927e8b22fad7c3012585aa02ba329d0ed69c6d35a2f60fbf80e57186bf0d9b9
- transaction
- 366a3181053c2b5a7eb2f7279de4b5c5ecbe50bebfd23d360dc8363c334e8071computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56146
the chainentry 56146
- sealed to the entry before
- 51a74f4790c5aefd63d18617921bfa24fd4a0b889180a887ef704a7d24cec7bb
- this leaf
- 61f31371a4e91f2ccb8f1657c6ecbcfff11a6582190af4f01d4cac512ea3b0d3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VmTN8CyNVlJvHTfV6yLSe1oblAvdFzWZjCgqoHocnppoumbDz7wI59NTVmzBPcJcwxyu/Vey43aD+fnV0jT3Dw==