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
- 15717ecb729197777aaea082fae04c9e4bcea9ca373d9a0106887820e9a279cc
- request
- e5fe50292c2be1264e9189c292d0db583feca934d4e1b74891d93562bf020138
- transaction
- abf38f4faa0a295eba516c0369cdfd79f201af82da4883f54de4cba14c079d25computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40114
the chainentry 40114
- sealed to the entry before
- a6283bafe6c1835516a1c06621ee0470f7b5741c97ac0165dc8cb0fae1360907
- this leaf
- 958a7677d8e236925431319d047ac5532d9b0753dfa80777d298cf6f0a961a8f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 25USx4W6C3po4NKXQHBmHIlllgqzSVj10r7BaZCUxjkoCfkSB0GgZdgBcl959k0azwDUywL1abgTO9+D0UzmCA==