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
- 130e9bd4257de688bc67bdaa997798bd927067fad3d8f752afc5b8cd1cd00719
- request
- c448c8d66c316a6747e3a138f06e54c59c90299656fcba4c1fe06ac8f4219b74
- transaction
- 071a2f9bf107411fbe5a3bab67c98a0b15e8b69e06881cc6e35bed328fa86512computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33053
the chainentry 33053
- sealed to the entry before
- 95f516bf10479a172f6d933e275429db7763b3f5b8ec42bb6bc07da82b1c4086
- this leaf
- c3d3384e4a6fee5333cbf206bc1f39bc87da0e20693515c1bffad8968af42eca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c5L00IEJr+RcAmkXTkzk0zzsiX+Jf4BtX2EG+9X4Kx0tTelsKhFFp13sHqeWgEp/+/8OE4yiVtVOgxBBpBUcDw==