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
- 821079454dffbf66a1036c7303830852737e9d022cfaaa6209e99bc9fe03771c
- request
- 6da101434ee57d63b57648a4b63d5da1221a677ee157be73fc6dd06fcc643d3f
- transaction
- 32f11d16f3645daf710698ab30f6623cc62639a44c2a695be3409831ecdb4725computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20392
the chainentry 20392
- sealed to the entry before
- 6d377775cf9e7c512db4b28da65cd383aedd4a799da3f1c74ec104f0787de3f0
- this leaf
- 0ab43a490eec6556c5202c698dcf0d340aa1033e0e8366e17100587f20d0d38a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H7HJJWDDd5JCbKhZy3BYczydFS4w+114oaPpnuDcYBO7LDPyMUwoUewS0htp6VBWRF4xByk37rXY6hqG+khMCQ==