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
- 359370b325dcffefc43fd64afba26927b5bb0bc30d675c9b666781b9789e671e
- request
- 6aa75d241de2ed068dc310003462ec94180513f78dd625eaf0ed97a00051f37f
- transaction
- ae69590f9237c5a130749518b5ee2961e369fbe945e4fe7ba7dfd2e51a9cdf29computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1690
the chainentry 1690
- sealed to the entry before
- cf6a711fbdcc6be1f99838dd3b1cf494948c4197e13f728f2128951fa30146ef
- this leaf
- d000afd0347240231c5c24adf8b86728fc8197d2fd58c54eed5144d63fd683a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X7dQDrxzLlEar74KtnZPP48t28jsgaPFa2a+DuYPUv/iu0ieWe7bBolAM91FOgoCQMg4z73bk5gEyunA/w+pDg==