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
- b3c2369ab0f70e82f5bc1b7dc2dcd7d6e836986986bbfa503a0603ee67f49af6
- request
- f6fe52aca7ca3753b43b3f5addc141e3532cbef855edd68b3253a2d6a8cbf71a
- transaction
- 7f719152ae3e7689bed88a1ab27a1171bfad133207df09285f7d2d970ef86144computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63157
the chainentry 63157
- sealed to the entry before
- 75e41508a7ed3302d1835f9033b5bcc6ded165ce523e35792009e93dbafefbfc
- this leaf
- 01fb0fac2c92ee23b5307659f597d23a95e19bd1e54657cd700e1505fb2c2130
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- J65VBqTuIUYHWI9A/OTLKLNGEeFDyWw5ftUsKWpNw8UZT+U6KoMYhulh94sysWJ3NzxEfaCSm9tP0dI06IrCBQ==