Availability

Fields

• siteCode string required

  A unique code for the site currently in use. A site codeSite code The unique code for a site registered under a merchant. A site is a place to transact: a website, or a branch of a store. A merchant can have several, and each transaction names the one it belongs to, so sending the wrong code files the payment against the wrong place. is generated when adding a site in the Ozow merchant admin section. [Please contact support for SiteCode - support@ozow.com]

  max length50
• dayType integer int32 required

  The day type. Possible options are:

  • Weekday = 0,
  • Weekend = 1,
  • PublicHoliday = 2,
  • Saturday = 3,
  • Sunday = 4
• fromTime string date-time required

  PayoutPayout Money sent from a merchant to a bank account. Unlike a refund, a payout is not tied to a payment anyone made you, so you can pay anyone with a bank account. Payouts draw on your float rather than on your incoming payments, and they are not self-service: they need approval from Ozow and testing in staging first. availability starting time.

• toTime string date-time required

  PayoutPayout Money sent from a merchant to a bank account. Unlike a refund, a payout is not tied to a payment anyone made you, so you can pay anyone with a bank account. Payouts draw on your float rather than on your incoming payments, and they are not self-service: they need approval from Ozow and testing in staging first. availability end time.

• isRtc boolean required

  Whether the availability is for real time clearingReal-Time Clearing Payments that clear immediately rather than waiting for a batch. A batch run settles at set times through the day; a Real-Time Clearing payment moves the funds between the two bank accounts as it is made, so the recipient can rely on them straight away.PayInc (RTC) or not.

• availabilityType integer int32 required

  The payoutPayout Money sent from a merchant to a bank account. Unlike a refund, a payout is not tied to a payment anyone made you, so you can pay anyone with a bank account. Payouts draw on your float rather than on your incoming payments, and they are not self-service: they need approval from Ozow and testing in staging first. availability type. Possible values are:

  1. Available - the payout will be processed during the current day.
  2. NextWorkingDay – the payout will be processed on the next business day.
  3. NextDay – the payout will be processed on the next day.
• batchScheduleType integer int32 required

  The payoutPayout Money sent from a merchant to a bank account. Unlike a refund, a payout is not tied to a payment anyone made you, so you can pay anyone with a bank account. Payouts draw on your float rather than on your incoming payments, and they are not self-service: they need approval from Ozow and testing in staging first. batch type. Possible options are:

  1. Scheduled - set times batches (e.g. 10am, 3pm).
  2. Interval - ongoing interval based batches.
• batchScheduleTime string date-time required

  The next payoutPayout Money sent from a merchant to a bank account. Unlike a refund, a payout is not tied to a payment anyone made you, so you can pay anyone with a bank account. Payouts draw on your float rather than on your incoming payments, and they are not self-service: they need approval from Ozow and testing in staging first. batch run time.

• batchIntervalMinute integer int32

  The frequency of payoutPayout Money sent from a merchant to a bank account. Unlike a refund, a payout is not tied to a payment anyone made you, so you can pay anyone with a bank account. Payouts draw on your float rather than on your incoming payments, and they are not self-service: they need approval from Ozow and testing in staging first. batch runs, in minutes.