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
- 300479b36fee5840d264b3c55842e2a9139ebb4c5df9fa93058b884a431b70e6
- request
- 673a30581e9b47c200b0e3a3a168c6f4e8f6d2eb214cb996bec806da483e2aea
- transaction
- eb6c476600c447d81fbb0439833d169f61649a6504397c9a12cc07e50a3bfb52computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53103
the chainentry 53103
- sealed to the entry before
- a2146d1f242985d7445b73f5ef86db9f92d1956bac19d00f58f5f33b71ef4f41
- this leaf
- 4487d2cfbf9de573f0cda7eec493f1a3ea71beddc6ebc3beaf0a712b73125304
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kGAuoa8LP0hKNpKsUuG2EV0UyA5aYko6NtckjAAYjC33WutzrVetFCPgQ/LAkYu6JDxLdRdZzdTdstLt3LbtBg==