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
- 2bdb710a725fcda9647beb5ebd354b3619327dadf605ca323cdf8f80df7acf77
- request
- 4a1c7fd7e894c1d9b62de19476ca2efd34dc9cb0350b27f9e951c964d6a0190a
- transaction
- c3b77cc70eae96f722aba9af4008fc446d9ab94dd59c3f20f337511db4eda20ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28134
the chainentry 28134
- sealed to the entry before
- fdb0d45acba5140f43bb4463cb0ec919987922275784ab26641de244b7b61e6d
- this leaf
- db0219c8ea6739f0e18c4a61580fc7a33cd7f1d40308b1e967cf135e556bd915
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xQMmqN0RBHpNt65K44EoSX4dD9iTY1D3kzawtn2Hy2I2EfIjL7M5if6I4Z9nhO+8FcsYgVWPQOAs11Un5Gv1Aw==