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
- 41167d1d48273957b93f9c974810561eeeba92bbf4083ec59ef0e296ea256144
- request
- ec6f645ab1c58cdc4a1b4cdf8fd1564d076df11ddcf22741d208bf7adee3be21
- transaction
- 3f3c1191949fb04f62378b44cc7bc8b21418a809a6cf14de2aea2bf487ced043computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58656
the chainentry 58656
- sealed to the entry before
- 70b34c97337fa7bc926ad71452db7c800390a4c0fbd994c133bb0a1fa3f6b1a6
- this leaf
- ac48db6cd6fc1c82461290b3a0ec392a76f67a48636ae315ee19dd5986fb79ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gwS7q1OXl1nDvfoZLOSI8xhm6ShkL0tLDYXQbH32x8DoZVa4zWfaQlQQ3FK4c02EJ0EpRbKH3Cn2zqPfJZFfAw==