Supported Transfer types: co-branded Verified Account A bank -> Verified Account B balance Verified Account A bank -> Unverified Account B bank Verified Account A bank -> Verified Account A balance Verified Account A bank -> email address Verified Account A balance -> email address Verified Account A balance -> Verified Account A bank Unverified Account B bank -> Verified Account A balance white-label
var cron = require('cron'); | |
var cronJob = cron.job("0 */55 * * * *", function() { | |
User.find({ | |
where: { | |
dwolla_id: '812-196-0757' //query user in db | |
} | |
}).then(function(user) { | |
if (user) { //if user exists in db | |
var rToken = user.dwolla_refresh; //grab the existing stored refresh token |
var express = require('express'); | |
var router = express.Router(); | |
var request = require('request'); | |
var c = require('../config'); | |
//step 1 | |
var redirect_uri = c.host + '/oauth_return'; | |
router.get('/auth/dwolla', function(req, res) { | |
var scope = 'Transactions'; | |
var client_id = c.client_id; |
<?php | |
$url = 'https://uat.dwolla.com/oauth/rest/offsitegateway/checkouts'; | |
$dwollaJson = array( | |
'client_id' => '*******', | |
'client_secret' => '*******', | |
'callback' => 'http://requestb.in/164go6s1', | |
'redirect' => 'https://purple.com', | |
'orderId' => 'test123', | |
'test' => 'false', |
{ | |
"id": "0bf1fd1b-92ef-e783-1f8b-3b0ae0d64016", | |
"name": "Dwolla API Sandbox", | |
"values": [ | |
{ | |
"key": "client_id", | |
"value": "", | |
"type": "text", | |
"enabled": true | |
}, |
Each webhook sent by the Dwolla API contains an Event with _links to: the associated resource, account associated with the event, and the customer associated with the event (if applicable). It is important to note that a single API request can trigger multiple webhooks to be fired, e.g. initiating a transfer from an Account to Customer can create the events transfer_created and customer_transfer_created.
Reference additional information on account types in this resource article.
Use this doc as a reference to map out the sequence of events your app will receive based on the account type(s) involved in the transaction as well as where the funds are coming from and going to (bank or balance). The following transfer scenarios are covered in this doc:
Transfer scenario 1 - Source: Client Account
bank Destination: Unverified Customer
bank.
Transfer scenario 2 - Source: Unverified Customer
bank Destination: Client Account
bank.
Both success and failure cases will be shown as well as additional information on what occurs in the event of a bank transfer failure.
General recommendations: Webhook endpoints may occasionally receive the same event more than once. We advise you to build in logic to protect against duplicated events by making your event pro
Each webhook sent by the Dwolla API contains an Event with _links to: the associated resource, account associated with the event, and the customer associated with the event (if applicable). It is important to note that a single API request can trigger multiple webhooks to be fired, e.g. initiating a transfer from an Account to Customer can create the events transfer_created and customer_transfer_created.
Reference additional information on account types in this resource article.
Use this doc as a reference to map out the sequence of events your app will receive based on Customer type(s) involved in the transfer as well as where the funds are coming from and going to (bank or balance). The following transfer scenarios are covered in this doc:
Transfer scenario 1 - Source: Verified Customer
bank Destination: Verified Customer
bank.
Transfer scenario 2 - Source: Verified Customer
bank Destination: Unverified Customer
bank.
Transfer scenario 3 - Source: Unverified Customer
bank Destination: Verified Customer
bank.
Both success and failure cases will be shown as well as what occurs in the event of a bank transfer failure.
**General recommend