Payment Gateway Error

API Support Funding Sources
42

Hi Shyam, I removed your application Key from the above comment since it’s considered highly sensitive information that needs to be stored securely, at least in Production.

As for the request body, there is no Dwolla GUID in there that I can use to search in my logs. Is your sandbox account set up under the same email that you’re using to sign up here? If so, I can just use your email address to look up the account!

43

yes i am using shyamsunder.sharma@5exceptions.com for Sandbox account

44

Thanks Shyam!

Looking at the logs, it looks like we had a blip in the Sandbox environment this morning that caused transfers to fail due to no services being available to receive the request.

The services are back up again and I am able to create transfers in my Sandbox test account. Would you be able to try creating transfers again?

As an aside, you should be able to catch the error and get the JSON response-body for errors. You can try wrapping the request in a try/catch and display the error response by calling the getResponseBody() method.

Example:

try{
    $new_customer = $customersApi->create([
        //request_body   
    ]);
} catch (Exception $e) {
    echo 'Caught exception: ',  $e->getResponseBody(), "\n";
}

Let me know if you run into any issues!

45

Thanks, its working now,

How to change unverified funding-source to verified in Sandbox

i wait for your reply

46

Hi @shyamsunder.sharma – you can verify a bank in one of the following ways,

47

Thanks @shreya ji

i am using this doc for PHP integration & it works fine for me.

1 Like
48

@shreya

I am getting following error when initiate transfer:

  1. code: 400
  2. file: “dwolla/dwollaswagger/lib/ApiClient.php”
  3. line: 320
  4. message: “[400] Error connecting to the API (https://api-sandbox.dwolla.com/transfers)”
49

Hi @vikas , would you be able to move this to a try catch and log out the exception as referenced in Shreya’s reply above? It looks like the error response body may be getting swallowed and not returning a very helpful response.

50

@shreya,

Thank so much for your quick response. As per your suggestion, I kept the code in try catch block and received the below response for your reference.

[DEBUG] HTTP Request body ~BEGIN~
{“_links”:{“source”:{“href”:“https://api-sandbox.dwolla.com/funding-sources/6cb298c8-edf5-4697-aa14-0581c059c27b”},“destination”:{“href”:“https://api-sandbox.dwolla.com/funding-sources/be4816ba-aeba-46f7-9f9a-b1cc89550b49”}},“amount”:{“currency”:“USD”,“value”:50}}
~END~
[DEBUG] HTTP Response body ~BEGIN~
{“code”:“ValidationError”,“message”:“Validation error(s) present. See embedded errors list for more details.”,“_embedded”:{“errors”:[{“code”:“NotAllowed”,“message”:“Receiver cannot receive from sender.”,“path”:“/_links/destination/href”,“_links”:{}}]}}
~END~

  • Trying 104.18.125.12:443…
  • Connected to api-sandbox.dwolla.com (104.18.125.12) port 443 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • successfully set certificate verify locations:
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: /etc/ssl/certs
  • SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305
  • ALPN, server accepted to use h2
  • Server certificate:
  • subject: C=US; ST=California; L=San Francisco; O=Cloudflare, Inc.; CN=dwolla.com
  • start date: Jun 9 00:00:00 2021 GMT
  • expire date: Jun 8 23:59:59 2022 GMT
  • subjectAltName: host “api-sandbox.dwolla.com” matched cert’s “*.dwolla.com”
  • issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3
  • SSL certificate verify ok.
  • Using HTTP2, server supports multi-use
  • Connection state changed (HTTP/2 confirmed)
  • Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
  • Using Stream ID: 1 (easy handle 0x55eeae2fb9d0)

POST /transfers HTTP/2
Host: api-sandbox.dwolla.com
user-agent: php-swagger-1.7.0
accept: application/vnd.dwolla.v1.hal+json
content-type: application/vnd.dwolla.v1.hal+json
authorization: Bearer cmljvg89EGl3s67TqILFq63uxtokmz8vTVfyfRNiuPj6xdLHub
content-length: 272

  • Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
  • We are completely uploaded and fine
    < HTTP/2 400
    < date: Mon, 21 Mar 2022 16:35:50 GMT
    < content-type: application/vnd.dwolla.v1.hal+json; profile=“http://nocarrier.co.uk/profiles/vnd.error/”
    < content-length: 252
    < access-control-allow-origin: *
    < x-request-id: cfefbc0e-932a-4d23-a18f-92c718682c6a
    < cf-cache-status: DYNAMIC
    < expect-ct: max-age=604800, report-uri=“https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct”
    < set-cookie: __cf_bm=K_8ldcvhjS1sNUGmHRkn7x5At2Dj_MuF5nLClPiN6z8-1647880550-0-AVjNvsRTpcqup7dJpWgyIN0Mod6bwkP1OOKHmK/fFw0535HpqjmbZxk+vFRPT9iRXgZ05n5LiYPbhy14DaToZO8=; path=/; expires=Mon, 21-Mar-22 17:05:50 GMT; domain=.dwolla.com; HttpOnly; Secure; SameSite=None
    < server: cloudflare
    < cf-ray: 6ef81a607f8d8c35-EWR
    <
  • Connection #0 to host api-sandbox.dwolla.com left intact
    {“error”:true,“message”:“{"code":"ValidationError","message":"Validation error(s) present. See embedded errors list for more details.","_embedded":{"errors":[{"code":"NotAllowed","message":"Receiver cannot receive from sender.","path":"/_links/destination/href","_links":{}}]}}”}
51

I noticed, why it says “Receiver cannot receive from sender.” however, I sent funding source URL properly for sender and receiver both. Kindly suggest me so that I can move forward.

52

Hi @vikas , as referenced in our developer documentation on Customer types, a transfer between two parties requires that at least one party must be CIP verified. It is your decision about which party completes this process based on your business model. If you are facilitating a transfer between two different users, at least one of them needs to be onboarded as a Verified Customer.

Sandbox Receiver cannot receive from sender