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
- 1ff1e1b00def15a6dc7b799ea204e4f024dba2a2ac027e764172c82f3f1b58bd
- request
- 24aab4bcc75edc2cc4ff5b625b458c3e48e2fc35959d7661a2f2ddc75cef6584
- transaction
- 637082a90c8460af13cddd6915a6b7e475dccbd49676d280912f1ba53fec7ceccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74946
the chainentry 74946
- sealed to the entry before
- 8496a8b9049b48fdaba995a6f093b3a8e21da5e6b202e46d28f2d01950c3b9e0
- this leaf
- 89a0375201fab7e4ee725d3faba0ea3c797dbe6b68222396bc0ef34503c2f794
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HiYZHQ6PrPH5yDhTjyECTdCw17HPAP2eORiEqg4RCEQkwAs5zhTC8uD+ZAonvZwfenPLkwZBKZ2iSUybPXQbBg==