Allow using encrypted payload with Cloud API

[jsyrjala]

Is your feature request related to a problem? Please describe.

We'd like to use encrypted payloads with Cloud API. Especially we'd like to receive encrypted async responses in Event notifications. And seems that responses would be encrypted if we would encrypt our requests. But currently SDK doesn't allow specifying encryption details.

With local api you can give EncryptionCredentialDetails

public interface ITerminalLocalApi
  {
    SaleToPOIResponse TerminalRequest(
      SaleToPOIMessage saleToPoiRequest,
      EncryptionCredentialDetails encryptionCredentialDetails);

    Task<SaleToPOIResponse> TerminalRequestAsync(
      SaleToPOIMessage saleToPoiRequest,
      EncryptionCredentialDetails encryptionCredentialDetails,
      CancellationToken cancellationToken = default (CancellationToken));

    SaleToPOIResponse TerminalRequest(
      SaleToPOIMessage saleToPoiRequest,
      EncryptionCredentialDetails encryptionCredentialDetails,
      RemoteCertificateValidationCallback remoteCertificateValidationCallback);

    string DecryptNotification(
      string notification,
      EncryptionCredentialDetails encryptionCredentialDetails);
  }

With cloud api there is no way to give EncryptionCredentialDetails

  public interface ITerminalCloudApi
  {
    SaleToPOIResponse TerminalRequestAsync(SaleToPOIMessage saleToPoiRequest);

    SaleToPOIResponse TerminalRequestSync(SaleToPOIMessage saleToPoiRequest);

    Task<SaleToPOIResponse> TerminalRequestAsynchronousAsync(
      SaleToPOIMessage saleToPoiRequest,
      CancellationToken cancellationToken = default (CancellationToken));

    Task<SaleToPOIResponse> TerminalRequestSynchronousAsync(
      SaleToPOIMessage saleToPoiRequest,
      CancellationToken cancellationToken = default (CancellationToken));
  }

Describe the solution you'd like

I'd like be able to specify encryption also with Cloud API

Describe alternatives you've considered

• Copying large parts of SDK and making it support encryption in Cloud API sound rather lot of work.
• Not having encryption in responses doesn't sound too secure.

[Kwok-he-Chu]

Hi @jsyrjala

• With Terminal API local communications, your POS app communicates directly with the payment terminal on your local network.

As you mentioned, you'll need to set up the EncryptionCredentialDetails (see docs).

• With Terminal API cloud communications, your POS app communicates with the payment terminal through the Adyen payments platform. In this case, Adyen handles the connection with the terminal for you.

There are two endpoints:

• The synchronous /sync-endpoint For this type of integration, you'll need to keep your HTTPS connection alive (the docs recommend 150seconds+), as Adyen will take care of the connection with your terminal.
• The asynchronous /async-endpoint If you do not want to keep the HTTP connection alive for this type of integration, you need to set up event notifications. There are two ways in which you can do this:
  • Using the Customer Area, see this documentation guide.

For this step, you will not require the EncryptionCredentialDetails from the library, but instead, configure the username, password, your server URL, and the `enableEncryption"-flag in the Customer Area. Event notifications will now be sent to the endpoint you specified. If you're using cloud communications with an asynchronous result, the Terminal API responses are also sent to this endpoint.

• Alternatively, you can use API calls (Adyen's Management API), see this documentation page.

Edit: I re-read your question, I thought you were asking about the event notifications. You want to send an encrypted response and expect an encrypted response back from the /async (terminal) endpoint and our interface is not supporting that behavior similar to the TerminalLocalApi-class.

[DjoykeAbyah]

Marked as stale. Reopen if this is still an issue.

[jsyrjala]

This is still an issue

[DjoykeAbyah]

Hi @jsyrjala!

Thanks for letting us know you're still experiencing this issue. I'll need to investigate this a bit further and I'll get back to you as soon as I know more.

Regards,

Djoyke Adyen