Hi There,
We (a card issuer-processor) are currently working on our API offering, which allows our clients (banks) to collect the encrypted Provisioning Authentication and Acticaiton Data from us and then pass it on to the X-Pays during push provisioning.
We are not using the In App Provisioning API, so we are building and encrypting the data manually. We have been following the documentation provided in "Banking App Initiated Provisioning - App Developer Integration Guide".
However, we would like to validate our implementation of the encryption. Is there some sort of test vector we may use?
ie.
Thanks,
Sean
Hi, @seanroutledge. Thank you for reaching out! Our agent is looking into this and will get back to you as soon as possible. In the meantime, if any community member has a potential solution, feel free to share it here.
Thank you for the response. I am eagerly awaiting the feedback
Hi there, I am still awaiting feedback from your agent?
Thanks
Hi @seanroutledge,
You mentioned that you're not using the In App Provisioning API. Please confirm which API product you are using for your project. For a list of our APIs, please click here.
Hi Diana,
We are a card issuer who have clients which are not PCI DSS compliant - they are the ones performing push provisioning via their own banking applications. Because they are not compliant - they are not allowed to handle unencrypted cardholder data - therefore when performing push provisioning they need us to generate the Provisioning Authentication and Activation Data and forward it on to them, so that they may forward it on to the relevant wallet during provisoning.
I hope that answers your question as to why we are not using an API.
We would just like to know if you have something available for us to confirm that the data we are encrypting is done so in the correct manner. The best way to do this is if you were able to provide test certificates, test data and the encrytped output so that we could run the data through our implementation and check that the encrypted data matches.
Thanks,
Sean
Hi @seanroutledge,
Please submit your inquiry via email to developer@visa.com for further assistance.