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
- bf0d5c752dc558a767982059e880e8ab77b165468aab62be0e8c2dac0921d25b
- request
- 8d9b7d28fe1c9236a2bccc97e5edf3ce3fdee2f3be5af095619c81314fa6983b
- transaction
- 41c405ec1dce5ace26ce02e17eddaa85a1e3fc8a6145c7a2e855899aaac618b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42650
the chainentry 42650
- sealed to the entry before
- a7bd93b01827a5d3ea2e90ca7b2c02e76a99b917b593266e705a8533ecb4be61
- this leaf
- 20d474c17859c227d44ebc2e426ecaa378679e9fe94c9a764243441b7ce0e30c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QwRViDNm3lvSQW8Kr31eL7w1drIYBquyVFxaza4voXpSWrROovDWie03EUAqJ24AC9e3HnWe4Tcunez3QGbHCg==