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
- 73be93f8d31360f6cb0fbf5528fc0fd851dbfe4a4a97f93a9e2306f8c90b45ca
- request
- 232273097bcee19f1a89b9012735301485a33d23010c7cfd40314abc219cfec8
- transaction
- 9e11b806988de022d7c15aaa22c1ff8499dd87dba7d2acd504faf452bdf20aafcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12012
the chainentry 12012
- sealed to the entry before
- de5a294aa0c11cbabf97319be79f59205b655885ff07c6bcb97401c8433d2639
- this leaf
- fe536a7c505d82522597a1ad865a49ad9770c953281f06d3e4747fdf38586288
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OSsTdtMwEiFsFFiow/rmMemDgx5yHX8EtWPjttlh6tXnxjbGGkp97kIiJcxz19lTAyomyGKLTHHZOjD3OksEDw==