BulkJobResultNotification

Fields

• JobId string uuid required

  The identifier for the bulk payment request job.

• JobReference string required

  The merchant reference for the job/batch that was passed in the create request.

  max length100
• Status string required

  The status of the job. Possible values:

  • Error - The bulk payment request job had encountered an error or the request data was not in the required format.
  • Complete - The bulk payment request job had completed successfully.
  • CompleteWithErrors - The bulk payment request job had completed but there were errors processing certain records.
• CompressedData string required

  A GZIP compressedGZIP A compression format. A large payload is compressed before it is sent and has to be decompressed before it can be read.Wikipedia JSON string of the JSON array of payment request fields. It carries the data from the create call with the result fields for each record added.

  The hash is built from this string compressed, exactly as it arrives, so verify before you decompress.

• Errors array of string required

  A summary of how the job went, as a single line. Sent on every notification, a job that completed cleanly included, so its presence does not mean the job failed. Read the per record result fields inside CompressedData for what went wrong where.

• Hash string required

  SHA512SHA-512 A hashing algorithm. Ozow uses it to sign the values in a request or a notification so you can tell that they arrived unaltered and came from us. Hashing is one-way: the hash cannot be turned back into what produced it.Wikipedia hash used to ensure that certain fields in the message have not been altered after the hash was generated.

  max length128