Create Expected Payment

post

https://recon.dapi.com/v1/expected

This endpoint enables you to add an expected payment. These payments are usually transfers you are anticipating your users to make to your business account.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Form Data

direction

string

required

credit or debit (credit = you are expecting money, debit = you are expected to transfer money) If you are expecting a payment from your user, it's a credit.

reference

string

The unique code you are expecting to match a payment with. The best practice is to enter a reference code when initiating a payment usind Dapi or asking the person sending money to enter it. Not all banks show the reference code entered.

account

string

The account ID you are expecting the payment to be sent to (or from if debit payment).

currency

string

required

3 character currency in ISO 4217 format. eg. USD, AED, GBP, BTC, ETH.

amount

int32

The numeric amount expected.

auto_reconcile

boolean

required

If set to false, we will match the payment but keep it as an expected one. You will need to access the Recon dashboard and confirm it.

webhook_id

string

The webhook id to be called when the payment is matched. (If auto_reconcile is false, it will only be called when you manually match the payment on Recon). You can add a webhook on the Recon dashboard.

webhook_payload

object

Some extra data in JSON format to be sent to the webhook URL.

date

string

The date in the following format YYYY-MM-DD.

counterparty

string

The counterparty you're expecting the payment from. While this is an optional field, we highly recomment you create a counterparty from each user you are interacting with (either transferring money to or expecting a transfer from).

from_amount

int32

You can enter an amount range instead of a fixed amount.

to_amount

int32

The upper range of the amount.

from_date

string

You can enter a date range instead of a fixed date.

to_date

string

Response

200