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
- a546f98ef6e63ca602cc3df500691a78d684444a860e6fd20856bb8ec754c42f
- request
- 4973c747ef728979068f1e9d95d7ea74b8a7a88b4d4e1ea139c52cdb1c4ee172
- transaction
- 271585dca1f77ff382febb57f8a6280d463016e3812ff4fea23f6a1d31389ef0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51959
the chainentry 51959
- sealed to the entry before
- bcaf1068961ce7a020019ac51dab5bb550598ef3d5789ae361c7db903f241ea7
- this leaf
- 10ca2203e66829b72a3902b9354611ea2817430e3dc0f6aecf8a1a7c4334e20e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b0qe9a54EIqhpZ7V0xHgr1l8IJ0d44Tp8eGUqmDLLzUe4W5BUvmn2k+QlWW6+RNjel8PxsAkNUKjBiMNcl4DCg==