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
- 4b9880ee5684245d27b7a04a73564fd3e2cd5175eeeb1807dd9af2a8b3a035de
- request
- beb6eb9a31a9040b5cdcc09d15ab3f7378bc3690a5925ca35bf774d557787053
- transaction
- e70b2720e5ae6b3b71d754679a08343251798f0e478d11fd5ec7048bfffb1253computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72185
the chainentry 72185
- sealed to the entry before
- 12ff36c5908216422cb71df3e94013fa014b4501379d20fa13dc58228c649908
- this leaf
- 6e823fc95161d84149e312fae53ce35e630e62f667bc44a53246d95b446811cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +4F4rYjy+Wwipx94g5wmZAN9b2FaCYDZjIw6Ea/hvsza7CNioyUaQKb9cAcaq6Q6HQ5vCkVwLlGAVq8yymw+AA==