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
- d09f5610f21db43c289e407c19a724a033399b609537b67c72477cdd0aef6566
- request
- 9ec3e475295dbd7fda86f06916f08b9f3cad5a8c7fa028dbbdf13e6520e17139
- transaction
- 77c82919c904d5f98d0c2070a95620b584d46bd685a2bd21e2e2f457d01a82ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60169
the chainentry 60169
- sealed to the entry before
- a816e77e788549e4fa8324a456c164cc3635ae999192766d767945b852218283
- this leaf
- 27d739fe2500f538a6547d5ef94a8f24ce2714bfce1134015edad4ade58005c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Mxojpd0/mg6K0mi9eFKdL6qAzYgspGi33hGb/jlPaHKEpol2pz9WAvXeWPvDRYyp9sp3qKEysrjU5B4/p1aCg==