Natural gives software agents a choice of bank payment rails

Natural announced a bank-rail option for payments initiated by software agents.

Natural announced Direct on October 29, adding a programmatic way for software agents to send domestic payments from a Natural wallet by ACH, wire or real-time transfer. The company says its real-time option uses RTP and FedNow and that customers’ existing Natural controls and limits continue to apply. Paper checks sent by mail and international wires are on the company’s roadmap. [Natural Direct announcement](https://www.natural.com/blog/direct)

Choosing a rail changes what happens after approval

Some business payments can wait for a batch. ACH can fit those transactions because the network processes transfers in batches and the recipient may have a standardized basis to return a payment. Real-time networks can settle around the clock. Their speed makes checking the recipient and amount before submission particularly important because a completed payment generally cannot be recalled through the rail. A wire may be appropriate when the amount or the recipient’s requirements make other options unsuitable. Exact availability, limits and timing depend on the payment and institutions involved. [Natural’s rail comparison](https://www.natural.com/blog/direct)

An agent may receive a vendor’s bank information and a due date only after a task is underway. Direct gives software a choice at that point. A business still needs a policy that says which recipients and rails are allowed, when an employee must approve a payment and what evidence to keep. A payment to an established supplier from an approved invoice has a different risk profile from a payment requested after an email changes the supplier’s bank account. [Natural’s service agreement](https://www.natural.com/nsa)

Handling uncertainty is part of moving money

A payment workflow needs to distinguish a rejected submission from a request whose outcome is unknown. If a connection times out after submission, sending the instruction again can create a duplicate. A safer design keeps an identifier for the original request and reconciles the transfer with the provider before taking any further action. It also records whether the requested rail changed between approval and submission.

Natural’s product announcement establishes a wider set of payment options for software. The meaningful operational question is whether teams can demonstrate that a transaction followed the approved instruction, observe what happened to it and handle exceptions without moving money twice. [Natural Direct announcement](https://www.natural.com/blog/direct)