email

Email is the fallback mechanism that when all else fails, allows you to remain compliant.

updateConfiguration

Here you can configure your VASP's email server to send outgoing emails.

Example

mutation {
  email {
    updateConfiguration(config:{
      smtpHost: "some host"
      smtpPort: 25
      smtpUsername: "some smtp user"
      smtpPassword: "some smtp password"
      smtpTlsSec: TLS
      fromEmailAddress: "from@my-vasp.com"
      notificationEmailAddress: "notification@my-vasp.com"
    }) {
      smtpHost      
    }
  }
}

registerVasp

Sending emails can only be sent to previously registered VASPs. Use this query to register email VASPs.

Example

mutation {
  email {
    registerVasp(vasp: {
      name: "Your Vasp"
      email: "changes_here@my-vasp.com"
    }) {
      email
    }
  }
}

distrustVasp

When the email option to a VASP is no longer required, use this query to remove it from the list. Previously sent transactions are retained.

Example

mutation {
  email {
    distrustVasp(id:"96e2d54c-4680-48be-ac17-30fb6aa17ae6") {
      id
    }
  }
}

registerTx

The same consideration hold here as with the registerTx mutation under the trpd object. Again, either addressLine OR street and number are required.

Example

mutation {
  email {
    registerTx(txDetails: {
      asset:BTC
      amount:"1230"
      txId:"68cf8b54b8af3e81c7d6186d20aada6a8896de4c9329b79427950b84334262ff"
      originator:{
          firstName:"some first name"
          lastName:"some last name"
        address:{
          country:"ch"
          town:"zug"
          postalCode: "1111"
          addressLine:"Dorpstraat 1"
        }
        customerIdentification:"some id"
      }
      beneficiary: {
          firstName:"some first name"
          lastName:"some last name"
        walletAddress:"123"
      }
      beneficiaryVaspId:"123"
    })
  }
}