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
- 68f591ccb44f3f1903d4a23ec0c8785fb2a2653b27c2ae75286b252f6fce560f
- request
- 863e155de60df145d92f83acb2345ca0d73cd6ccaef086f2a50030fc52c58251
- transaction
- 306cb5f993fc5df05995b9d340a8f19b4441c46b29464fe08fbca2d1b9e36998computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7458
the chainentry 7458
- sealed to the entry before
- 01811e2cc6f72ec55085c4b75ffb7cec22d7f69d3df765c8029fced0eacb3bc2
- this leaf
- 1e132cf2d8336e3d5b6639142a035da702b5363d64cee6a4497603c8d4a4b681
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H/BnenP473P//Pb0Q/KxyGO7tOJR64MGaHegSvhk06tSzX0bTTR8hQ7SC+0sKoqU79M4mYblZD+XGNZc71nvCw==