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
- fdb3162735e90fa04404446625322f671a717b4665a1e07ddca8a9fd850e6929
- request
- b1d1314fbff25cd83c842d57ade392cd4833b7b15dcd4a1f664a462a21caf4d6
- transaction
- d5d505106ab4a544a3b173faf6d91bdf7c02f0e57305a1eda1ec141e86fb967bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1655
the chainentry 1655
- sealed to the entry before
- 9847cb07b5b87c2e4ef4d46766ef448041c91407d34aa88732edadb90442c4da
- this leaf
- 89a8dc8638776536f9bcbbd5bb41fdeffd87f4780ac4feef76df2ff6cabfa2bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rL86ua0mrPactcHCO5xbgoWIfHr6nb7GpfFF37e8LqlBegzuV8+ktbRfA8tvtE3TrtJds6PqhEbKO5OdD2VrBw==