Konduto
Get started with Konduto
This page provides a comprehensive guide to successfully integrating Konduto with DEUNA.
Before you begin, you must complete the following steps to certify your account and credentials.
Requirements
The following content lists all the requirements for a successful integration with Konduto.
Test environment
You need the following credentials to test an integration with Konduto:
- API test credentials:
- Public key
- Secret key
- Dashboard test access:
- Email associated with your Konduto account.
- Password
Production environment
You need the following credentials to complete a production integration with Konduto:
- Konduto test environment certification.
- Productive Konduto account credentials:
- Email associated to your Konduto account.
- Password
- Access to the production Konduto API:
- Public API key
- Secret API key
- Your DEUNA credentials.
- Real card to perform tests.
Test environment certification
Konduto requires that you test the integration before using a production environment.
After you finish the test integration, you receive a certification from Konduto.
Your DEUNA TPM will accompany you in the communications with Konduto.
Integrate Konduto
Now that the technical requirements are set, you can start the integration.
1. Set up Konduto’s dashboard
Go to your Konduto account and review your API keys:
- Select Stores under the user icon.
- Select the edit button in your Store and then click Keys.
- Review that the keys are functional by toggling on Active?.
2. Create rules
After reviewing your API keys, create rules to test the integration.
Rules determine when a transaction is approved, denied, or needs a manual review.
Create rules for approve, deny, and manual review:
- Click the Rules tab.
- Click NEW RULE.
- Create the Always Accept Rule with the following values:
- Select Credit Card for Rule valid for payment method.
- Select OR for Type.
- Enter ACCEPT in Rule Name.
- Enter Accept by email in Description.
- Select APPROVE for Recommendation.
- Create the Always Review Rule with the following values:
- Select Credit Card for Rule valid for payment method*.
- Select OR for Type.
- Enter REVIEW in Rule Name.
- Enter Review by email in Description.
- Select REVIEW for Recommendation.
- Create the Always Decline Rule with the following values:
- Select Credit Card for Rule valid for payment method.
- Select OR for Type.
- Enter REJECT in Rule Name.
- Enter Reject by email in Description.
- Select DECLINE for Recommendation.
3. Configure the webhook
Now, connect Konduto with Deuna using a webhook:
- Select “Stores” under the user icon.
- Select the edit button in your store and click Preferences.
- Paste the webhook:
- https://api.stg.deuna.io/post-transactions/konduto for DEUNA staging environment.
- https://api.sandbox.deuna.io/post-transactions/konduto for DEUNA sandbox Environment.
- Click Save to finish.
4. Set up the DEUNA test environment
Add Konduto to your DEUNA Connections:
-
Go to the DEUNA Admin and toggle on Test mode.
-
-
Click Connections.
-
Look for Konduto and click Connect.
-
Enter your Konduto credentials in the pop-up window:
- Public key: Enter your Konduto public API key.
- Private key: Enter your Konduto private API key.
-
Click Connect.
A success message indicates Konduto is added as a connection.
5. Activate manual review
DEUNA needs to activate the manual review for Konduto integrations:
-
Go to the DEUNA Admin and click Mechant.
-
In General Fraud Settings toggle on:
- Enable Manual Review
- Enable Automatic Operations Execution
The two options allow DEUNA to automatically perform refunds, captures, or void payments after an anti-fraud post-authorization decision.
6. Set Konduto as post-authorization fraud processor
Konduto works for both pre and post authorization, but it is recommended to configure Konduto for post-authorization.
-
Go to the DEUNA Admin and click Payment Strategies.
-
On Default Processing, click the edit button.
-
On Define the order of trasnsaction processing, click the edit button.
-
Click Edit routing.
-
Toggle on Post authorization fraud analysis.
-
Select Konduto as an anti-fraud engine provider.
-
Click Save to finish.
7. Configure device fingerprint
Configure the fingerprinting as a last step before conducting tests.
Depending on your integration, follow the next steps in coordination with your DEUNA TPM
VTEX
- Follow the steps in VTEX fingerprint.
- Use the Konduto public key in the
fraudCredentials
object:
fraudCredentials: JSON.stringify({
KONDUTO: {
"publicKey": "Konduto Public Key"
}
})
Direct API Integration
-
Follow the steps in Device fingerprint.
-
Use the Konduto public key in the
fraudCredentials
object:fraudConfig: { MERCADOPAGO: {}, //example of a PSP that requires fingerprinting KONDUTO: { publicKey: "Konduto Public Key" } },
Device fingerprint is not available for payment widget or payment link integrations.
8. Test the integration
Perform the integration tests:
# | Case | Rule | Use Case | Acceptance requirements |
---|---|---|---|---|
1 | Automatic approval | Transaction with DEUNA using the email [email protected] | 1. The buyer uses the email [email protected]. 2. Select DEUNA to make the payment. 3. Fill out the information and complete the purchase. | 1. The transaction is approved in DEUNA. 2. The transaction is approved in Konduto. 3. The transaction is approved in your store. |
2 | Automatic disapproval | Transaction with DEUNA using the email [email protected] | 1. The buyer use the email [email protected]. 2. Select DEUNA to make the payment. 3. Fill out the information and complete the purchase. | 1. The transaction in DEUNA is denied. 2. The transaction is denied on Konduto. 3. The transaction is disapproved in your store. |
3 | Manual Analysis - Manually Approved | Transaction with DEUNA using the email [email protected] | 1.The buyer use the email [email protected]. 2. Select DEUNA to make the payment. 3. Fill out the information and complete the purchase. 4. The merchant logs into their Konduto and DEUNA panel to validate the pending transaction. 5. The merchant manually approves the transaction. | 1. The transaction in DEUNA is approved. 2. The Konduto transaction is approved. 3. The transaction in your store is approved. |
4 | Manual Analysis - Manually Declined | Transaction with DEUNA using the email [email protected] | 1.The buyer use the email [email protected]. 2. Select DEUNA to make the payment. 3. Fill out the information and complete the purchase. 4. The merchant logs into their Clearsale and DEUNA panel to validate the pending transaction. 5. The merchant manually declines the transaction. | 1. The transaction in DEUNA is rejected. 2. The transaction on Konduto is rejected. 3. The transaction in your store is rejected. |
5 | Manual Analysis - Keep it in Analyzing state | Transaction with DEUNA using the email [email protected] | 1.The buyer use the email [email protected]. 2. Select DEUNA to make the payment. 3. Fill out the information and complete the purchase. | The transaction in Konduto remains as Pending. |
For manual reviews, follow these steps:
-
Go to your Konduto dashboard.
-
Click the Orders tab.
-
Look for the transaction in pending status.
-
Click Pending to change the transaction status.
-
Select the status from the dropdown list:
- Approved
- Declined
- Fraud
- Not Authorized
- Cancelled
-
Enter comments if needed.
-
Click Save to change the transaction status.
9. Send test evidence to Konduto
In coordination with your DEUNA TPM, send an email to Konduto with the evidence of the performed transactions.
Dear Konduto Team,
We attach evidence of DEUNA tests in our test environment:
1. Automatic approval: 1xxxxxxx123
2. Automatic failure: 1xxxxxxx123
3. Manual analysis - Manually approved: 1xxxxxxx123
4. Manual analysis - Manually declined: 1xxxxxxx123
5. Manual analysis - Keep in Pending status: 1xxxxxxx123
We await your confirmation to activate the test in production.
Best regards
Estimado equipo de Konduto,
Adjuntamos evidencia de las pruebas con DEUNA en ambiente de pruebas:
1. Aprobación automática: 1xxxxxxx123
2. Reprobación automática: 1xxxxxxx123
3. Análisis Manual - Aprobado Manualmente: 1xxxxxxx123
4. Análisis Manual - Declinado Manualmente: 1xxxxxxx123
5. Análisis Manual - Mantenerlo en estado Pending: 1xxxxxxx123
Esperamos su confirmación para realizar la activación en producción.
Saludos
Prezada equipe Konduto,
Anexamos as evidências dos testes com DEUNA em um ambiente de test:
1. Aprovação automática: 1xxxxxxx123
2. Falha automática: 1xxxxxxx123
3. Análise Manual - Aprovado Manualmente: 1xxxxxxx123
4. Análise Manual - Recusado Manualmente: 1xxxxxxx123
5. Análise manual - Mantenha em status Pendente: 1xxxxxxx123
Aguardamos a sua confirmação para ativá-lo em produção.
Saudações
Konduto will respond indicating that you can move forward with the process in production.
10. Repeat the process in production
Now you must repeat the process in your Production environment.
The following content provides the production URLs and credentials needed for the integration:
Configure the webhook:
Paste https://api.deuna.io/post-transactions/konduto for DEUNA production Environment.
Set up DEUNA
Toggle off Test mode and use the following credentials:
- Konduto API production credentials:
- Public API key
- Secret API key
Configure device fingerprint
Use Konduto production keys in the fraudCredentials
object.
Test the integration
After the testing process, send the testing evidence to Konduto.
Send evidence of at least three transactions to Konduto.
Use available cards to perform productive tests.
11. Send the production evidence to Konduto
In coordination with your DEUNA TPM, send the productive transactions to Konduto in the same email.
Konduto will send an email to validate that everything is correct.
Updated 3 days ago