Wire In

Learn how to fund your Localpayment account via Wire In transfers from external banks. Choose between API integration for automation or the Dashboard for manual processing.

Wire In

Overview

A Wire In is the process of transferring funds from an external financial institution's account to your Localpayment account. This transaction type increases your Localpayment account balance and is reflected in all account reports and statements.

Wire In transactions impact supplier account balances and provide complete transaction visibility through account statements and reporting dashboards.

You can process Wire In transactions through two methods:

How Wire In Works

The Wire In process follows a structured workflow to ensure secure and accurate fund transfers:

  1. Wire In Request - You initiate the transfer via API or Dashboard
  2. Pending Review - Transaction status changes to "Pending_Credit"
  3. Operations Validation - Our operations team reviews and validates the transaction details
  4. Processing - Once validated, the transaction proceeds to completion
  5. Completion - Status updates to "Completed" and funds are credited to your account
  6. Notification - You receive confirmation of successful transaction completion
⚠️

Important: Wire In transactions automatically expire after 14 days if not completed.

Receipt Requirements

Upload your wire transfer receipt in one of these supported formats:

  • PNG, JPG, JPEG (images)
  • PDF (documents)
  • TXT (text files)

Prerequisites

Before initiating a Wire In request, ensure you have:

  • Wire transfer receipt - Proof of the external transfer
  • Valid API credentials - With proper authorization permissions
  • Complete transaction details - All required sender and recipient information

API Endpoint

To create a settlement, send a POST request to the Create Wire Inendpoint.

Endpoint

POST https://api.stage.localpayment.com/api/account/wire-in

Authentication

Include your access token in the Authorization header:

Authorization: Bearer <your_access_token>

Key Request Parameters

The request requires several key parameters:

ParameterTypeDescriptionRequired
transactionTypestringMust be set to "WireIn"
currencystringCurrency code (e.g., "ARS", "USD")
countrystringCountry code (e.g., "ARG", "USA")
amountnumberTransfer amount
accountNumberstringYour Localpayment account number
toobjectRecipient bank details
fromobjectSender bank details

Example Request (Argentina)

curl --request POST \
     --url https://api.stage.localpayment.com/api/account/wire-in \
     --header 'Authorization: Bearer <your_access_token>' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '{
  "transactionType": "WireIn",
  "currency": "ARS", 
  "country": "ARG",
  "amount": 50000,
  "comment": "Monthly funding transfer",
  "externalId": "258648ed-df89-422c-9eb0-e585014ed65e",
  "accountNumber": "032.032.00000082",
  "to": {
    "name": "BANCO DE GALICIA Y BUENOS AIRES S.A.U.",
    "swift": "GABAARBA",
    "address": "Av. Hipólito Yrigoyen 155, X5000 Córdoba, Argentina",
    "accountNumber": "0070119655111901676653",
    "accountName": "Localpayment",
    "beneficiaryAddress": "Av. Hipólito Yrigoyen 200, X5000 Córdoba, Argentina"
  },
  "from": {
    "name": "BANCO DE LA NACION ARGENTINA",
    "swift": "NACNARBA", 
    "address": "Av. Hipólito Yrigoyen 35, X5000 Córdoba, Argentina",
    "accountNumber": "0110119655111901676653",
    "routingNumber": null,
    "accountName": "John Doe",
    "beneficiaryAddress": "Av. Hipólito Yrigoyen 10, X5000 Córdoba, Argentina",
    "intermediaryBankName": null,
    "intermediaryBankSwift": null,
    "intermediaryAccountNumer": null
  }
}'

Response Handling

Success Response

When your Wire In request is accepted, you'll receive a detailed response:

{
  "transactionType": "WireIn",
  "externalId": "258648ed-df89-422c-9eb0-e585014ed65e", 
  "internalId": "0f1d47dc-e9c6-4fdf-8ba1-c9b39116574d",
  "country": "ARG",
  "currency": "ARS",
  "clientCode": "0001",
  "creationDate": "2024-12-28T13:47:58.808+00:00",
  "errors": [],
  "status": {
    "code": "100",
    "description": "PENDING_CREDIT", 
    "detail": "WIRE IN"
  },
  "accountNumber": "032.032.00000082",
  "amount": 49500,
  "fees": {
    "description": "Processing Fee",
    "currency": "ARS", 
    "amount": 500,
    "account": "032.032.00000082"
  },
  "localTaxes": [],
  "withHoldings": [],
  "comment": "Monthly funding transfer"
}

Key Response Fields

FieldTypeDescription
externalIdstringYour unique transaction identifier
internalIdstringLocalpayment's internal transaction ID
creationDatestringTransaction creation timestamp (ISO 8601)
amountnumberNet amount after fees
feesobjectApplied processing fees
statusobjectCurrent 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:

Common Status Codes

CodeStatusDescription
100PendingCreditPending Credit
200CompletedCompleted
717RejectedByBankRejected
📝

Note: For complete status code reference, see the 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

Next Steps


Support & Resources

Need assistance with your payout cancellation integration?

  • Technical Support: Contact our support team for integration help
  • API Documentation: Complete endpoint reference and guides
🚀

Pro Tip: Use our sandbox environment to test Wire In workflows and ensure your integration handles all scenarios correctly before going live.