Quick start
This guide shows the process of a frictionless authentication, using the Software Express 3DS Server REST interface.
#
What you'll need- Active account on 3DS Server's homologation environment (obtained with our support team)
- A tool capable of performing HTTP calls, such as Postman, REST Client or cURL
#
Creating the transactionClick here to see the full Open-API ("Swagger") file for 3DS
HTTP method: POST
URL: https://mpi-homolog.softwareexpress.com.br/3ds-server/v2/authentication
Headers:
- Content-Type:
application/json
- merchant_id: {your merchant id}
- merchant_key: {your merchant key}
Request:
Response:
Learn more about this service.
#
Performing the authenticationClick here to see the full Open-API ("Swagger") file for 3DS
HTTP Method: PUT
URL: https://mpi-homolog.softwareexpress.com.br/3ds-server/v2/authentication/**{3DS Server transaction ID}**
Headers:
- Content-Type:
application/json
- merchant_id: {your merchant id}
- merchant_key: {your merchant key}
Request:
Response:
Learn more about this service.
Attention - About the new version "/3ds-server/v3" (in development):
Soon, Fiserv will launch a new version of the APIs (/3ds-server/v3) for 3DS usage, incorporating the HMAC (Hash-based Message Authentication Code) model for authentication, authorization, and integrity assurance of requests. The HMAC signature (generated hash) must be sent via the HTTP header "Authorization" and the HTTP header "Auth-Token-Type" should be added with HMAC as its value. The technical specification on how to generate the HMAC signature is available at the link: HMAC Generation.
Additionally, in this new version of the APIs (/3ds-server/v3), it will be necessary to include the HTTP header "Client-Request-Id", containing a UUID v4 (Universally Unique Identifier version 4), randomly generated according to RFC 4122 specifications, for unique identification of the request. To learn more about UUID v4, see: https://www.rfc-editor.org/rfc/rfc4122.
Comparison between versions:
Para /3ds-server/v2
Content-Type: application/json
merchant_id: {your merchant id}
merchant_key: {your merchant key}
Para /3ds-server/v3
Content-Type: application/json
Client-Request-Id: {UUID version 4}
Authorization: {HMAC signature}
Auth-Token-Type: HMAC
merchant_id: {your merchant id}
merchant_key: {your merchant key}