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
- 4f5c592eebd04efd2ef238db7b1f8c354164d6607e86a63e259b196bbdceaab0
- request
- d9caaf73bb21cb057163c344da2053505d7175fd851871507c45d369f8ea2eaa
- transaction
- fbb47f1d20da5546846ac617925384b6e067b91df590048fa8eb27de5a7dfa73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 101
the chainentry 101
- sealed to the entry before
- 7fac55e8231305a6f36bb71030b3b72aaa222e2d6eeb6affe55de758663f876f
- this leaf
- 79b95460466c0c4924d1e0dd19318dff96626325c207122e2ce3d35736faded8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FI8wckoszXA4pbcdVMQ8NWTdxVfwilnBqmZiLVFj/hhU4Nm6/yQnM9So42jtQShoQADHKwbAQdYlF3tyx2atBA==