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
- 85ce316a059fd71267230b7cfc3b97635532e367516c6643c2e25b1644e6a453
- request
- 67c58b8644136699535ab62e94da290ae3fb4ccd41eff31ceee17f78fb222708
- transaction
- 04063c6ad0e1fe3afa168b8b0e234d62080a6c45003d6e334070bb8dc856fa87computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32254
the chainentry 32254
- sealed to the entry before
- 27e43b809b21fe2f006ecd97cc7e174ce1bdefaf283969c162a13fe3a22adc83
- this leaf
- 11ae1a2fd1f652db363d9b43ba9bf371d40c69368263858f8b2b18c1dad26046
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iRjm+BCnddVRNyqisP7rJcjoH6+5lNUWXylVGhiPife7tQBQRYHaY5M/SRuu+dg+ScHd+6zRXhJXVg1BjQDeCw==