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
- b310c7286944c6196a52482a184afdf8394c3ad3d8172dc16ec66e2d43fe2681
- request
- 75a3579df7c98bd945541e1d8094bdbc0e76c308f3105ddcc4a88b18875d45e5
- transaction
- 1ed502385524e64d040a49ae328cbd3fd26b3663be2eed481c7f4ecd4e902083computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1033
the chainentry 1033
- sealed to the entry before
- e4adc6131b5bdb8a58cf57bf8a4deb0b5889673a18109f43f377337e3b71c0eb
- this leaf
- b693b54e507ad2efb6cca24f81425142a1a121778da181789980e4d5f15badf1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HZU360EN773g3hemxtmp4y2M8f9NoLlq2ko+H8C3o9WbbIE2nxjxyVMWhB54SIm7hQaVzMF65ZoufqJlNbZfAQ==