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
- 0cd6a90fdd280d00146fe29d6a87293b107b265733883d3b6f57fcf1725eaf6f
- request
- d724f181b2aaba301d8121f07fb53a588a5cd70f56598f6e4050991e2003d231
- transaction
- a5116834fd13b3ea2bffc02a450fff2b616d229753168e75a70ff60b32e62f2dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77649
the chainentry 77649
- sealed to the entry before
- 1c1779e86d49757fd6b5322d6905835afa489d3ddbc6766cb07e167189faf734
- this leaf
- b054b3a704c72686922294316ee45a7710315675bebd5d3366429a533cedee87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +gSg1Gd0HWvB1IWHIGQdYHzlijv2Nf9cUOr0i9Asb1tQsCa0xJhI6sKYVKMa1XJ30eZOUt1kqwMBEMGkJCNjDA==