About routing number issue

API Support Funding Sources
1

Hello sir/ma’am

I used dwolla in our application for bank-to-bank transfer, but when I entered my routing number (9 digit) in add funding source(add bank) it’s give me error like these :-

code: “BAD_REQUEST”
description: “Routing number must be exactly 9 characters.”
status: “ERROR”

Please help me to out of this issue, this is our routing number = 123000220.

No we are not including any spaces or special characters.

{
“accountHolderName” : “xyz”,
“accountNo” : '123456789",
“accountType” : “CHECKING”,
“name” : “US BANK”,
“routingNo” : “123000220”
}

This is our payload of add funding source api.

2

Hi @Amee_Patel , are you running into this error is Sandbox or Production? Also, could you share the Customer Id please?

3

Hello ma’am,

This error is running in production.

Customer id is = 52a5d8b4-0f2d-4fdb-9017-aaca4ebe5d18

thank you

4

Hi @Amee_Patel, thanks for sharing the Customer ID! I can confirm that we’re seeing attempts to add a funding-source to that customer, all failing with the statusCode 400. I also checked the routing number and it passes the check in Sandbox.

I wonder if the the actual request body being sent to the API is being manipulated in any way from what you shared above. Is there any way you could share the raw request/response bodies from your logs (PII and account number redacted)?

5

What is the actual issue of this routing number, it’s from dwolla api side or other issue.

Please tell me the actual problem.

Thank you

6

I sent it in the beginning of the chat.

7

Hi @Amee_Patel

The error is definitely from Dwolla, however the routing number you shared above isn’t the one that’s being sent in the API request. The number being sent in the raw API request does not have 9 digits. Would you be able to check the request to create a funding-source and try again? Please prompt the user to enter the full 9 digits of their Routing Number.

8

I already checked my request and this issue is running in this routing number only if you entered another routing number it’s working fine, then also I will check one more time.

9

Hello ma’am,

I checked my request about routing number. It is correct. Now tell me what can I do for that issue?

Thank you

10

Hello ma’am,

I found one more issue about that customer.

{
  "code": "ValidationError",
  "message": "Validationerror(s)present.Seeembeddederrorslistformoredetails.",
  "_embedded": {
    "errors": [
      {
        "code": "InsufficientFunds",
        "message": "Insufficientfunds.",
        "path": "/_links/source/href",
        "_links": {
          
        }
      }
    ]
  }
}```

The customer get this type of error when he is transfering the amount. He is trying to transfer $1135.

Why it thrown Insufficient funds error while he is tranfering amount in his account
11

Hey @Amee_Patel , regarding the routing number errors, I was able to dig into the API request logs for those requests. The request-body we were receiving were as follows:

{
    "bankAccountType": "checking",
    "routingNumber": 1.2300022E8,
    "accountNumber": 1.XXXXXXXXE11,
    "name": "us bank",
    "accountNo": "XXXXXXXXXXXX",
    "routingNo": "123000220"
}

Two things to note here:

  1. The accountNo and routingNo fields aren’t Dwolla attributes, these fields will get ignored and not taken into account when creating the funding-source.
  2. The actual Dwolla attribute of “routingNumber” is set to 1.2300022E8. It has an alphabet and a period sign in the value which are both not accepted.

Please update the above request-body and make sure you are only passing us the fields mentioned in our API reference

{    
    "bankAccountType": "checking",
    "routingNumber": "123000220",
    "accountNumber": "XXXXXXXXXXXX",
    "name": "us bank",
}
12

As for the Insufficient Funds error, I looked at the logs for this one too. The failures I am seeing are for the attempts to transfer funds from your Main Account’s balance to the Customer. This error was sent because you do not have enough funds in your Balance to fund the transfer.

Were you perhaps meaning to make a transfer from the Customer’s bank to your balance? If so, the Customer’s bank will need to be verified first, using one of the bank verification methods we support, then use the customer’s funding-source URL as the “source” and your balance url as the “destination” in your transfer request.

Similar to the funding-source creation request, you are sending information not pertinent to the transfer API request:

{
    "amount": {
        "currency": "USD",
        "value": 1009.08
    },
    "_links": {
        "account": null,
        "self": null,
        "events": null,
        "customers": null,
        "about": null,
        "source": {
            "href": "https://api.dwolla.com//funding-sources/4db801e5-d485-48ef-855e-1e9b3b2929f4",
            "type": null,
            "resource-type": null
        },
        "destination": {
            "href": "https://api.dwolla.com//funding-sources/3d594023-a5c0-4489-b9ef-61e06ac43025",
            "type": null,
            "resource-type": null
        },
        "webhook-subscriptions": null
    }
}

Please remove all the attributes that have the value of null.

13

Ok I will fix that…

thank you for your kindly help :innocent:

14

About transfer issue I got it by yesterday itself.

Again thank you.

15

But ma’am,

{
    "bankAccountType": "checking",
    "routingNumber": 1.2300022E8,
    "accountNumber": 1.XXXXXXXXE11,
    "name": "us bank",
    "accountNo": "XXXXXXXXXXXX",
    "routingNo": "123000220"
}

this payload was working in another customer. The api give 200 ok response and funding source is also added.

If payload is wrong then, why it is working for another customer in production
16

Hi @Amee_Patel,

Hmm…if there’s a successful resource creation, the API responds with a 201 Created HTTP status code.

Could you share the Customer ID? I can take a look at the raw request to see what we received.

17

sure ma’am