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
- 034a83b654062111226389c1be34be74edbdd732298b46dfc29d5a263814ab49
- request
- d70bd9e411cb9715bc2995753dac57d096d612365289e5e2f26becd6e8086593
- transaction
- 4ebba7282069d1bc2ef7ed06ae5588cb8177082a5875b97d140e3e80cc02b364computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45988
the chainentry 45988
- sealed to the entry before
- 3908f795e3e2e34c303da55890afe96e6f6f31c4da18aabd3cd943dbbe5a2fca
- this leaf
- 61e199e19a72c0820d200b297c8f18f0e1550042bafc7b6eb36a86708b9acc00
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9ggpii6Wjz2Fc2A1BHLVvvXk1eseLGois0GLzqGiM9J/YNjQHII+RfoO0h0+//DSX2EH+Ka+SrAeR5eg1P5zAQ==