At Unnax, nothing makes us happier than being able to offer you quality service. To that end, we need to guarantee that your system is well configured and ready to handle communication with our APIs and other tools that are at your disposal.
The certification process will vary slightly depending on what services you wish to implement in your production environment, but most of the protocols are very similar:
- We will provide you with information to initiate an interaction test with our systems
- The results from the test are shared with our integration team
- The results are verified by our team and the test is determined to be successful or unsuccessful.
Which of our services would you like to certify?
In order to validate the correct implementation of our Account Aggregation services, we need to make sure that you have completed certain tasks related to Webhook configuration, API integration, information reception and interpretation, and overall usage of our endpoints in the Integration Environment.
We will check if you have registered the webhooks related to this service:
We will verify if our callback responses sent to the endpoints registered in the webhooks for ‘fitnance_read’ receive a “200 OK” from your servers
Read content interpretation:
We will require random data related to one or more statement entries. We will give you an order_code and you will have to return the information related to its amount, concept, and many other data that you could find in the bank read response.
If you have implemented multi-bank reads through our widget, we will verify that you have performed successful reads of two or more banks in a single bank read request.
Categorization (If implemented):
We will require you to give us the total amount related to a specific category for an account read
Incoming Payments (Payment Initiation)
Our Payment Initiation-Incoming Payments service will allow you to receive funds in different ways: debit card payments, credit card payments, and direct bank transfers. The certification process depends on which of these variants you intend to use.
We will check if you have registered the webhooks related to the Pay In services:
- event_payment_transfer_lockstep_authorized (Direct Bank Transfer)
- event_payment_transfer_lockstep_completed (Direct Bank Transfer)
- event_payment_creditcard_preauthorize (Credit Card Payments)
- event_payment_creditcard_pay (Credit Card Payments)
- event_payment_transfer_external_completed (External Payments)
Created transactions and handle results:
Here we will be validating that you are able to create transactions and that you can handle the responses they generate, both for successful and failed transactions. In order to do this, we will provide you with information for certain transactions that you will be making. For both types of results (Success and Failed), you will be asked to provide us with some information found in the callbacks responses. This information will allow UNNAX to certify the correct implementation of the Pay In services.
Credit Cards and Debit Cards:
If you are implementing Debit or Credit Cards Payments we will need to confirm that you can initialize the Widget and perform:
- Tokenized transactions
As said, after each test we will require information about the result of each transaction so we can confirm the test success.
Direct Bank Transfer:
When integrating Direct Bank Transfers we will be certifying that you can perform transactions using either the Widget or the API services. Take into consideration that transactions with 2 step login process and 2 step signing process will be tested.
For the external payments testing, we will require you to create an external pay in order. You will then receive a callback with the result of the transaction, and we will request certain information from this response to verify the functionality is implemented correctly.
When testing hosted payments, you will be generating a campaign schedule to start in two days from the test date. That campaign will contain at least five different orders. We will confir that the orders and the information related to them were created as expected.
When a campaign has been successfully confirmed, we will ask you to stop it to complete the tests.
Outgoing Payments (Payment Initiation)
In order to validate the correct implementation of our Outgoing Payments service, we need to certify that you have completed certain tasks related to Webhook configuration, response to our callback events, integration with our API, and comprehensive usage of the UNNAX Portal related to the Outgoing Payments services.
We will check if you have registered the webhooks related to this service:
Created transactions and handled results
Here we will be validating that you are able to create transactions and that you handle the responses they generate, both for successful and failed transactions. In order to do this, we will provide you with information for certain transactions that you will be making. For both types of results received (Success and Failed), you will be asked to provide us with some information found in the callbacks responses. This information will allow UNNAX to certify the correct implementation of the Outgoing Payments service.
Retry a transaction in state error
When a transaction goes to the error state, you will have the option to retry it; you can do this through the portal or through our API. UNNAX will set transactions in this state and will provide you with the order_code so you can perform the retry action.
Cancel a pending transaction
When a transaction goes to pending/new state, you will have the option to cancel it; you can do this through the portal or through our API. UNNAX will set transactions in this state and will let you know the order_code so you can perform the cancel action.
Our Identity Verification services will allow you to verify the authenticity of an ID number, an Identification Document, or determine whether a person is present on an SDN (Specially Designated Nationals) or PEP (Politically Exposed Persons) list, which are used for anti money laundering (AML) purposes. The tests that we will run will vary depending on which of our services you wish to use.
With the AML service, you will be able to verify whether a person is listed on a blacklist. In order to certify the correct implementation of this service, we will provide you with a set of credentials that will return specific results from the requests you make. We will require some of this information to validate the reception of information and its interpretation by your systems.
Our Full ID service allows you to verify the authenticity of an ID document and automatically extract the data contained in it. The Full ID service uses two differentiated endpoints: one to create a request to validate the document, and another to receive the results.
- Full ID Request:
To validate this endpoint, we will provide you with a set of IDs and we will check for the creation of the request in our systems. If the requests are created correctly, the test will be complete.
- Full ID Request Details:
This endpoint will give you the information resulting from authentication and evaluation of the ID card. In order to validate that you have implemented this endpoint correctly, you must provide us with the JSON resulting from the details request.
The Simple ID service will let you check the ID Card and the name of a person in the Spanish treasury's database. To perform this task you only have to integrate the Simple ID POST endpoint. To validate that you have implemented this service correctly, we will give you a set of credentials and you will have to send us the response information of the call.