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
- a1b3067313a18fc320742574885ef311a2fc78faa12f213488fde6e2f0a2b71f
- request
- 7ee298bd372895923a34a94839a8dc66f8735e30f761953dd7d15efae28be7e3
- transaction
- 2add31a097a44995bd48920658364fe9bdfdbd317367c9e5fdc4a9e65e61b0c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69007
the chainentry 69007
- sealed to the entry before
- 518649add9faf1f578ec49a5606c771b4b6ca187b50265534b5784e45147f19c
- this leaf
- 2be6bb7725f410e2060fb38880a4be5d3df754f9e3f01f4571a1ae88c54be0e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vn2Rm9x9g9wSa+mTd2BuwOucEE7lZeESc8p5zB2yj00pCdrQx3Q3Y2b3EBeD6/Yk7yFGQfp09imiVfZmvL6UBw==