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
- 59107399011d36c7673345f536cfb9b8309bbdc14f03e07599b06fa37851f945
- request
- 1a825b8285b37c7097b07683966f21783c05be81d3938d0cce10e9d405467a15
- transaction
- 3c9a50a97b3eabdb256ed5bd7587dbc6ce3c1db706fb059b8d252f3842c9dae9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70026
the chainentry 70026
- sealed to the entry before
- dca7c4337439c0dd68b0298911258f62a2a51398b1c9c546023ef60e9f0767ad
- this leaf
- 0ba8528e785330713083ad6951570e3b4b259d2633662c1fe1919c9566595e57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NXBws3/BLFoaIoc2zPlF+5fo6lrYJgd+gMbigeyd4HNTWs/mH5kDQvJvJweNJl0Vnp6BUvSu+mMfj9+wLwULDA==