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
- d36df04c3228f8865e2fa7ca794fb7e21915f96c79ebed399422ed7f5a43f88a
- request
- c881b83d05e8ec77590efd9df36a49b6e22c668c5029804fc7f6975bf3259d8b
- transaction
- a3548248bedc4d902f7234837db10706b70afd47d9a384440635635cb8901653computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1068
the chainentry 1068
- sealed to the entry before
- 3c19c5ec77f4acd5d2cf0ec9cff93e294513ba0bd606278569796790a6f19490
- this leaf
- 3cbfc176482b3c62793d9a5e18f189b8ce12792a7a9ff56185417ef94a6a7a44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pOvq22wIOgf+HEbsL3EH27ClRky6d4jBF6bygUMgSEYD+MqPCW1EBjeUQky0EcG/toNQ6LoO44hUPvbR+TUPDA==