Incoming Wire In Notification
Notify Localpayment of an incoming wire transfer using our API to settle your account balance. This guide walks you through initiating a notification, handling API responses, and tracking the transaction status.
For transactions in Fiat currency (e.g., USD, ARS, MXN), you are required to notify us of the incoming wire. This can be accomplished via:
- API Integration: Recommended for automated, programmatic notification.
- Localpayment Dashboard: Use the web interface for manual notification of individual transactions.
Important
The Wire In notification process is not used for Stablecoins. Instead, please follow the Stablecoin Wire In flow.
This guide covers the API workflow end to end, from notification to final settlement.
Before You Begin
Before notifying a Wire In, ensure you have:
- Wire transfer receipt: Proof of the external transfer.
- Valid API credentials: With proper authorization permissions.
- Complete transaction details: All required transaction information.
API Endpoint
To notify a settlement, send a POST request to the Create Wire In endpoint.
Endpoint
POST https://api.stage.localpayment.com/api/account/wire-inAuthentication
Include your access token in the Authorization header:
Authorization: Bearer <your_access_token>Key Request Parameters
The request requires several key parameters:
| Parameter | Type | Description | Required |
|---|---|---|---|
transactionType | string | Must be set to "WireIn" | ✅ |
currency | string | Currency code (e.g., "ARS", "USD") | ✅ |
country | string | Country code (e.g., "ARG", "USA") | ✅ |
amount | number | Transfer amount | ✅ |
accountNumber | string | Your Localpayment account number | ✅ |
to | object | Recipient bank details | ✅ |
from | object | Sender bank details | ✅ |
Example Request (Argentina)
curl --request POST \
--url https://api.stage.localpayment.com/api/account/wire-in \
--header 'Accept: application/json' \
--header 'Authorization: Bearer 123' \
--header 'Content-Type: multipart/form-data' \
--form 'request={\"transactionType\":\"WireIn\",\"currency\":\"BOB\",\"country\":\"BOL\",\"amount\":100,\"comment\":\"Comment\",\"externalId\":\"a11h7890-78ju-098j-hu78-124ftn8lo0io\",\"accountNumber\":\"068.068.00000183\",\"to\":{\"name\":\"Bankname\",\"swift\":\"BCBHDOSD\",\"address\":\"BankAddress\",\"accountNumber\":\"1310825187\",\"accountName\":\"BeneficiaryBankName\",\"beneficiaryAddress\":\"BeneficiaryAddress\"},\"from\":{\"name\":\"OrderingBankName\",\"swift\":\"BICAARBS\",\"address\":\"OrderingBankAddress\",\"accountNumber\":\"123456789\",\"routingNumber\":null,\"accountName\":\"accountName\",\"beneficiaryAddress\":\"BeneficiaryAddress\",\"intermediaryBankName\":null,\"intermediaryBankSwift\":null,\"intermediaryAccountNumer\":null}}' \
--form [email protected]Response Handling
Success Response
When your Wire In request is accepted, you'll receive a detailed response:
{
"transactionType": "WireIn",
"transactionFlow": "wireInAutomatic",
"externalId": "a11h7890-78ju-098j-hu78-124ftn8lo0io",
"internalId": "b97fe1cd-50d3-4ee2-8a6e-34ee6d7e4f4e",
"country": "BOL",
"currency": "BOB",
"clientCode": "0001",
"creationDate": "2025-12-04T21:07:41.689+00:00",
"errors": [],
"status": {
"code": "101",
"description": "PENDING_AUTH",
"detail": "Pending Auth"
},
"accountNumber": "068.068.00000183",
"amount": 97.32,
"fees": {
"description": "Fee",
"currency": "BOB",
"amount": 0.5,
"account": "068.068.00000183"
},
"localTaxes": [
{
"code": "0016",
"percentage": 2.18,
"description": "FNA",
"currency": "BOB",
"fxSource": 6.911493,
"fxQuote": 0.0,
"amount": 2.18,
"account": "068.068.00000183"
}
],
"withHoldings": [],
"comment": "Comment",
"code": "101"
}Key Response Fields
| Field | Type | Description |
|---|---|---|
externalId | string | Your unique transaction identifier |
internalId | string | Localpayment's internal transaction ID |
creationDate | string | Transaction creation timestamp (ISO 8601) |
amount | number | Net amount after fees |
fees | object | Applied processing fees |
status | object | Current transaction status information |
Error Response
Validation Error Example
{
"externalId": "089c81c6-7be2-4798-8e53-d4bfff61f852",
"errors": [
{
"code": "404",
"detail": "This beneficiary account is invalid"
}
],
"status": {
"code": "404",
"description": "REJECTED",
"detail": "This beneficiary account is invalid"
}
}Track Transaction Status
After submitting a wire in, monitor its progress through these methods:
Webhooks (Recommended)
Receive real-time notifications when transaction status changes. Most efficient for production environments.
Status API Endpoint
Query transaction status programmatically. Useful for polling or recovering lost webhook notifications.
Dashboard View
Visual interface for monitoring transactions. Great for manual oversight and detailed transaction analysis.
Common Status Codes
| Code | Status | Description |
|---|---|---|
100 | PendingCredit | Pending Credit |
200 | Completed | Completed |
717 | RejectedByBank | Rejected |
Complete Reference
View all status codes in our Transaction Status Documentation.
Security Recommendations
- Always use HTTPS for API requests
- Store access tokens securely (never in client-side code)
- Implement proper error handling and logging
- Validate all input data before sending requests
Resources & Next Steps
Maximize your integration success with these essential resources
Webhook Integration
Set up real-time notifications for transaction status updates.
Reporting Dashboard
Access detailed analytics, reporting tools, and reconciliation features.
Transaction Monitoring
Learn to query transaction status and implement comprehensive tracking.
API Reference
Complete endpoint documentation with interactive examples.
Pro Tip
Always test your workflow in our sandbox environment before deploying to production. This ensures your error handling, webhook processing, and status tracking work correctly across all scenarios.
Need Help?
Contact our support team if you experience any issues or need assistance for integration.
Updated about 19 hours ago
