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
- 1e70e2443e6cca60ffd4d01993f42900d71d194b613612f531976c981b049a59
- request
- ca02f7570a26d14f5ec31503c8389bcd1fda5641d76aee0e1f2b90e26d23fd11
- transaction
- ab38321398cce790249c7f13307545a31f21441546c6363de2fa3a3ac6f1f25fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48670
the chainentry 48670
- sealed to the entry before
- 4210d0db040ee1d398447b556d05c16eeec286dae64548282e03cedd18f00ade
- this leaf
- 011b09bcce1c98368c2e085f90e9145151ca1e4bfb37b921c686108dda1f0c88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sP8RUFmDi6zDX/PZiikxtmKaYWalfRapQq3XWm77vj78OCgmYCF9v5JnZphxlsnBPBI457PAPQgoRzcQ43/mCA==