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
- 3361c2fb512a1f493bacfe243e54d904983269e121acafde2ce16d4ecf58ba75
- request
- efc7c2e6dfeef6af6061a150ca83208bbda61a79a4150e2e3abc99445ceb13fd
- transaction
- 84ee3d6bbcb5b5fd0658ade83d1af3c1220b0addebe632decfc9904428e544c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26905
the chainentry 26905
- sealed to the entry before
- 478a54b78fcc5eb03bfd1d53b23fe970bd1befefe005f3c55ee486de660bcc6e
- this leaf
- 20e5995e4164ae8b398fcf26ceca209db4c22e71d501bb9671c16d8da419d09b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VtKLAu702Xtxj/s0n4QKbqp7J6IOQ+4Xe4fkobZU0EWGTwuN0YSf7uCPwEEKvMtnPRkOtKlTLZ0Zn/d40gy+DA==