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
- edca3cc4dda0603411ae8d96c2798c05c79cc6df514bd4bfaada253c2463e020
- request
- bf3ad43e0bf77dbf2124c5bcd06dfa3aa75d95f9b70b97423d2ab4fa4cb0fa6b
- transaction
- 0b017a45cc44a91227d4a1828dfdeef8b654f0ce85abfa5dfd9507ded84b70cbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74983
the chainentry 74983
- sealed to the entry before
- 6d5d46a6ee664bbb20fb8bfe11af4fe6bebfc576991b54b593beda51dd3c58c8
- this leaf
- 1a9cb94469121abade14b11a03042165e8de9602befe6df86a2ecfd1e69a7cad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wgGlOysqu/5FDRjer8xL/nhukXe7vVZ8XyayWK+GMIVvmlqjg6dLNDfmZfpwar44QltkM7BBMimhjvJL330sDg==