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
- d86bc057e508492a56904306d36d5130a53d66d0eb4ba8349e33b942db4aab48
- request
- 519cadec467d8aefd53622fdb502510a04892f327a2a52601e0009d249639fe1
- transaction
- c158a9aa80119f6c9e73c1302344134d043b02bb4e74c2d722c0dcba7163ec83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1360
the chainentry 1360
- sealed to the entry before
- 1eac69737dc4dbdace4c9d6b43b6293904f8b53a9a8dd6c919daac498b9b70b1
- this leaf
- ca2603b0805514f30faeedaf3b69c82949fb1248ca69829881648b3989feac8b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5Vc99n+EkLWQPipZVtM8djWG8w8/GCRA2DEWC7fzJNbKlsLBPaRggxnWGDiQtETJiIn8xf0V8oeXEg/Q5U4NAg==