Deuna App Wallet Configuration
Overview
This guide covers the merchant-side configuration of Deuna App Wallet in the Deuna Admin Panel. Configuration is a one-time setup that determines which payment mode your customers will use.
Accessing Configuration
Step 1: Log In to Deuna Admin
- Navigate to DEUNA's Admin
- Enter your merchant credentials
- Click Log In
Step 2: Navigate to Payment Methods
- In the left sidebar, go to Connections
- Click on Payment Methods
- Look for Deuna App Wallet in the list
Initial Setup
Enabling Deuna App Wallet
If Deuna App Wallet is not yet enabled:
- Find Deuna App Wallet in the Payment Methods list
- Click Enable or Add
- A configuration panel will open with a form to add the processor
- Fill in all four required credential fields (see section below)
- Select your preferred payment mode (see section below)
- Click Save
The payment method is now active and will appear as an option for your customers at checkout.
Adding the Deuna App Wallet Processor
When you enable Deuna App Wallet, you must add the processor with credentials from your Deuna App Wallet account.
To add the processor:
- In the Deuna App Wallet configuration panel
- Click Add Processor or Configure Credentials
- Fill in all four required fields:
Required Fields
| Field | Description | Example | Notes |
|---|---|---|---|
| Public API Key | Called "API Key" in Deuna App Wallet | pub_abc123xyz789 | Maps to the header x-api-key |
| Private API Key | Called "API Secret" in Deuna App Wallet | sec_abc123xyz789 | Maps to the headerx-api-secret |
| Point of Sale (CAJA) | Called "CAJA" in Deuna App Wallet | 4200069 | String identifier for your point of sale |
| Format | Payment code type | QR or CODIGO_6_DIGITOS | Determines if customers get QR or 6-digit code |
Step-by-Step Form
Important:
- All four fields are required
- Your credentials come from your Deuna App Wallet business account
- Format selection here determines the payment mode for all orders
- After saving, credentials are encrypted and stored securely
Choosing Your Payment Format
When filling the processor form, you must select your payment format. This choice is made when adding credentials and determines how your customers will interact with the payment flow.
Format Selection Guide
| Aspect | Numeric Code (CODIGO_6_DIGITOS) | QR Code |
|---|---|---|
| Customer sees | 6-digit code | Dynamic QR code |
| Time window | 3 minutes | 15 minutes |
| How to pay | Type into app | Scan or click |
| Best for | Desktop/tablet checkout | Mobile-first checkout |
| User experience | Manual entry required | Fast, one-tap/scan |
| Field value | CODIGO_6_DIGITOS | QR |
Format 1: Numeric Code (CODIGO_6_DIGITOS, 3 Minutes)
Choose this if:
- Your customers primarily use desktop/tablet
- You want a quick transaction window
- Your checkout flow runs on multiple device types
- You prefer simplicity and minimal dependencies
How it works:
- Customer sees a large 6-digit code
- Code expires in exactly 3 minutes
- Customer must open Deuna App and enter the code manually
- After entering, customer confirms in the app
- Payment confirmed via webhook
To select this format:
- In the processor form
- Under Format, select Numeric Code (CODIGO_6_DIGITOS)
- Complete the form and click Save Processor
Verification:
- Once saved, you'll see a confirmation message
- All subsequent orders will use 6-digit numeric codes
Format 2: QR Code (15 Minutes)
Choose this if:
- Your customers are primarily mobile users
- You want a longer transaction window for flexibility
- You prefer a modern, one-tap experience
- QR scanning is common in your target market
How it works:
- Customer sees a dynamic QR code
- QR code is valid for exactly 15 minutes
- Customer can either:
- Scan with the Deuna App camera
- Click to open the app directly
- Payment confirmed via webhook
To select this format:
- In the processor form
- Under Format, select QR Code
- Complete the form and click Save Processor
Verification:
- Once saved, you'll see a confirmation message
- All subsequent orders will use QR codes
Configuration Panel
Troubleshooting Configuration
Issue: Can't Find Deuna App Wallet in Payment Methods List
Solution:
- Refresh the page
- Check that you have "Payments" permission in your user role
- Contact Deuna support to ensure Deuna App Wallet is provisioned for your account
Issue: Processor Won't Save or Shows Error
Solution:
- Verify all four credential fields are filled:
- Public API Key (not empty)
- Private API Key (not empty)
- Point of Sale / CAJA (not empty, numeric string)
- Format selected (QR or Numeric Code)
- Check that credentials are correct from your Deuna App Wallet account
- Test your credentials in the Deuna App Wallet dashboard first
- Try again in a different browser
- Contact Deuna support if issue persists
Issue: Customers Can't See Deuna App Wallet at Checkout
Verify:
- Deuna App Wallet is Enabled (not Disabled)
- Processor is properly configured (all four fields filled)
- Customer's order is in USD currency
- Customer is in Ecuador (or using Ecuador billing address)
- Payment Widget includes
deuna_walletprocessor - Order token was generated successfully
If all verified:
- Contact Deuna support
Permissions & Access
Required Admin Roles
To configure Deuna App Wallet, your user account must have:
- Connections - Read/Write permission
- Payment Methods - Read/Write permission
- Webhooks - Read/Write permission (for webhook setup)
If you lack permissions:
- Ask your account owner or admin
- They can grant permissions in User Roles and Permissions section
Multi-Admin Setup
If multiple admins manage payments:
- All configuration changes are visible to all admins
- Any admin can change payment mode (not recommended without communication)
- Enable audit logs to track changes:
- Go to User Roles and Permissions
- Enable Activity Log
Best Practices
Configuration
✅ Do:
- Test webhook connectivity after setup
- Choose payment mode based on your customer base
- Review refund limitations before enabling
- Document your mode choice for your team
❌ Don't:
- Disable Deuna App Wallet without notifying your team
- Frequently change payment modes without reason
- Share webhook URLs in unsecured channels
- Assume mode selection can be overridden per order (it can't)
Monitoring
✅ Do:
- Check payment metrics weekly
- Review webhook delivery logs regularly
- Monitor refund requests for trends
- Test webhook connectivity monthly
❌ Don't:
- Ignore webhook failures for extended periods
- Skip merchant onboarding testing
- Forget to update webhook URL if your backend changes
Updated about 12 hours ago