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
- ebfb2326340c2709a38d9cb0e47cb668800a8916a5f8dd93d3219b5a323e51dd
- request
- db7710f0e8519759b151efd3ccf8c0080ffde511165c93195ffd0a5b8969c1cf
- transaction
- 52b0f39f82c08d6b10e4d709e49f564af925c62975c9443dd57b9005a085c90bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72046
the chainentry 72046
- sealed to the entry before
- 7918234d4932a1f4bbd1a4b80f797feb5b97b23714e8d7a8362cf783ca308f24
- this leaf
- 43e5afb59898bd61dc9b83e37dabe5e51b7106082566f7781d63b3ff7bd35b96
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9EG/Z47I4EbjbwCNuqhQKwAbd8kCzQJ35lNqCLfkLwyXKnrViXoKdviEIOCAdF7yJfkkdIlWiioTBa6uWX1EBQ==