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
- 0cf72ecc14cc458d048bf8f4cb969c7283aacd53199a63a06adbbea7bb5c3e55
- request
- 7ef3a764ab709bed5507344e2fac0e91cc4bb45932305dfc6612e94bba11e6ca
- transaction
- 2f8279f5f2aa4b5a73c180d3987dca2e3ec6c9be4125cc7f6132579186588ee4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23905
the chainentry 23905
- sealed to the entry before
- 5cccefe244bc36f8b6da203dc035e936f79fda31f03d96e6aad2691d10273eb0
- this leaf
- 679da2b5be1b891b6f0191f5a716aa99775bdfaae53abc100fad980d85d528f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5Vr8j7aqmjkcE3m/nADlPaYx0fheLuO/DIMRH/1wjVxykbkYJ4gUwflujLNH1bH2QQCm8nVfsS/URnAd6iOmCQ==