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
- f40d665edef0008aef74364bdae281ad5497e34c20796903eabb0c333c3758ee
- request
- 5b08f0cff0546b2d15526bc15f05dffdfb603185657474230cf6e5607f088e08
- transaction
- 7d6cbecd6c11ccb0f61fdd215d2356274857d491095adea6b62a41de72e58cd9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51269
the chainentry 51269
- sealed to the entry before
- d5e82e536777a2ea2233b10648dcc35ce41a40e988488de759c842856112a840
- this leaf
- 3c5be895e2490968beb3fa18e36b34b41011184bce2e629ae1fb9b9377560262
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PAXOEvPL3yKi2JenkNQWhxIRDoVLothUIQkxBrrpnPRn1em4dStPhJxEwHUE+qD0mr3tqmcQTByqH/rVPVoSAQ==