Skip to content

Expected payload from create KYC link API is different from what the API is really returning. #42

Description

@gberdugo

The actual implementation of the CreateKYCLinkResponse object is expecting that the JSON response from the Create KYC Link endpoint contains the "base64", "url" and "expiration_date" parameters, but the JSON returned from this API contains the "url", "base64_qrcode" and "expires_at" parameters instead.

Because of this, we are unable to retrieve the qr code and the expiration date for the KYC link.

Could you guys provide a fix to this issue?

Thanks!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions