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
- 680f0257cf4e277619fffaabf3742f2e78922e38982e442a1ca96dce4ec8701a
- request
- 4f59dc720c322ff7e06278686944291c6f3f85b32e24746b2b4a13508ac8efff
- transaction
- 57caaafb7c527379e7bc1596fc25e3677cf3b0629c49b48537540e009a06e14ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11466
the chainentry 11466
- sealed to the entry before
- aaa02ee34c6106fb381bec94732c0bf0a0eddbdc867f12961165b6a69e8c72f9
- this leaf
- 264d4fd7cc44d4a049e0e12bb434f3bebb8859680c204a27ebab752dd5203174
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9PBWcUokhWEs9Xm6U9fgTT5+XcLlFdxaOKUpSg0Bz1uAsuTRMALBPTPkCNSOOONHmQk2lYBJvXquuikfugXJBA==