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
- 4c87dd1b8cd2980276f8769101f5578013317675c0ade7211784c37c7a9a67e9
- request
- 3b5504cbeff11e7c5ea45dc124bebd3f770a3e0c02eddb0e6a6b78c62667eadb
- transaction
- b0a14c8c527076cb9961a74db2e8f70a35b255a13e87ccec77f2d33e675c497bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41519
the chainentry 41519
- sealed to the entry before
- 52a493715cf161e22a14fc8918614df56a256e77555ae5f9b7865873539dc6c8
- this leaf
- 9817d6e8fd49cdaca38d2707927b9f4e3cf6b9fc2c97cce003811c397eb98ae2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +ME44OK7j2Ai6RAMsQAXK4AutZcST2xwLA9/9rFyw0+g2VzAXomLK8EK3Rbvl1HedQYD3DacHufTZVucTaVzCA==