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
- 6300b274970f534ea57633b8e9bd3e433033b78a6b9bca842cf2624fc9f78c92
- request
- f64336c48490774bfd092c3550097047a14ef0b5b35df60102ff3afc7bf7daf2
- transaction
- bc9f408241f45a4d4a86338f6778203b1b9c75aa14d93ac83b637de9c6037e6dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66182
the chainentry 66182
- sealed to the entry before
- 94872bcf380056d5c5992d1a4a1dfa87312725d9f47859a22baf3861f2102811
- this leaf
- c144a0b8138c5fba0da015698829785dbcf015e2beee436540107958d6b51b84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9wx+HhmoL2MA2OXkEMNJftskwmKqnWwMa2WSykg7Nf5OJPlvbQn55mNwnal06mD1X7bhdaBdQ5Rs0Y6C4n2RDQ==