Payment Processors

The payment types that will be processed by the payment processor. Currently, ach is supported only.

The type of payment processor.

• achDirectUS - Peach system will create NACHA files and upload directly to lender’s bank SFTP.

A lender's identifier for an object.

After the object is successfully created, a lender can use ID or externalId identifiers to fetch the object.

To fetch the object using externalId you need to add ext- to the URL.

Note: Don't add ext- to the identifier value. For example: if the external identifier is ABCDE, then pass externalId=ACBCE and NOT ext-ABCDE when creating the object.

The name of the payment processor. For example: Silicon Valley Bank or Wells Fargo.

The status of the payment processor.

• draft - the payment processor is in the process of being configured and not ready to be used.
• active - the payment processor is ready to process payments.
• deprecated - the payment processor was deprecated, and new payments cannot be processed.

Mark the payment processor as default for the company. Only one payment processor can be default. If a new payment processor is created with isDefault=true and there is another payment processor with isDefault=true, the system will set isDefault=false for the other/existing processor.

The timezone used by this payment processor. For example: "America/Los_Angeles"

The cutoff time for ACH processing, in the payment processor's timezone. Use 24-hour format. For example: "19:00"

The cutoff time for ACH same day processing, in the payment processor's timezone. Use 24-hour format. For example: "10:00"

Data element that is part of the file header record. For example: 121140399.

Data element that is part of the file header record. For example: 1456726789.

Data element that is part of the file header record. For example: SILICON VALLEY BANK.

Data element that is part of the file header record. For example: PEACH FINANCE INC.

Data element that is part of the batch header record. For example: PEACH FIN ACH.

Data element that is part of the batch header record. For example: 2837461011.

Data element that is part of the batch header record. For example: 12773923.

If the value is NOT provided (aka null or empty) as part of the configuration, the system will automatically set this value to achFileHeaderImmediateDestination without the last digits. For example: if achFileHeaderImmediateDestination=121140399, the system will set achBatchHeaderOriginatingDFIId=12114039.

How the fee is charged by the payment processor. If the full amount is transferred, and fees are charged monthly, use gross. If fees are deducted from the amount transferred, use net.

The fee charged by the payment processor for regular ACH transactions. For example: 0.05

The fee charged by the payment processor for same day ACH transactions. For example: 0.50

The Standard Entry Class Code within ACH.

The hostname for SFTP. Host name should not contain a scheme, so don't put sftp:// on the front. You may optionally specify a port like so: example.com:222. If no port is supplied a default of 22 will be used.

The method used to access the sftpHostname.

• If usernamePassword, then sftpUsername and sftpPassword must be provided.
• If keys, then sftpSSHPeachPrivateKey and sftpSSHPeachPublicKey will be created by peach.

The username for SFTP.

The password for SFTP.

A json object of any algorithms that need to be disabled when accessing sftpHostname with a private key. This should be null in most scenarios.

The folder where files (e.g. ACH instructions) will be uploaded. The system will change directory into this folder before performing the upload.

The folder where files (e.g. ACH returns) will be downloaded from. The system will change directory into this folder before performing the download.

The name of the ACH confirmation file. The format is a regular expression. If you are not sure how to set up the regular expression, please contact the Peach team by providing a few examples of file names.

If the value is not provided, we assume that the processor doesn't support ACH confirmation files and any upload of an ACH file is considered as successful.

The name of the ACH return file. The format is a regular expression. If you are not sure how to set up the regular expression, please contact the Peach team by providing a few examples of file names.

• If true, files (e.g. ACH) will be named based on the ACHP_MMDDYYYYHHMM convention. For example: ACHP_110320211305.
• If false, files (e.g. ACH) will be named based on a custom implementation. Do not set false unless you’ve coordinated with the Peach team.

• If true, outgoing files will be encrypted with thirdPartyPublicKey and signed with peach's private key. Make sure to set encryptionMethodOutgoing and thirdPartyPublicKey values.
• If false, outgoing files will not be signed with peach's private key.

The encryption method that Peach system will use to encrypt the outgoing files from Peach. Keep the value empty if no encryption is needed. If encryptionMethodOutgoing is set, a value must be set for thirdPartyPublicKey.

The encryption method that Peach system will use to decrypt the incoming files to Peach. Make sure you use peachPublicKey to encrypt the files sent to Peach or uploaded to SFTP for Peach. Keep the value empty if no encryption is needed.

• If true, the peach keys for encrypting and decrypting incoming files to Peach are updated. The new peachPublicKey value is returned.
• If false, the peach encryption keys are not changed

A lender's identifier for an object.

After the object is successfully created, a lender can use ID or externalId identifiers to fetch the object.

To fetch the object using externalId you need to add ext- to the URL.

Note: Don't add ext- to the identifier value. For example: if the external identifier is ABCDE, then pass externalId=ACBCE and NOT ext-ABCDE when creating the object.

The name of the payment processor. For example: Silicon Valley Bank or Wells Fargo.

The status of the payment processor.

• draft - the payment processor is in the process of being configured and not ready to be used.
• active - the payment processor is ready to process payments.
• deprecated - the payment processor was deprecated, and new payments cannot be processed.

Mark the payment processor as default for the company. Only one payment processor can be default. If a new payment processor is created with isDefault=true and there is another payment processor with isDefault=true, the system will set isDefault=false for the other/existing processor.

The timezone used by this payment processor. For example: "America/Los_Angeles"

The cutoff time for ACH processing, in the payment processor's timezone. Use 24-hour format. For example: "19:00"

The cutoff time for ACH same day processing, in the payment processor's timezone. Use 24-hour format. For example: "10:00"

Data element that is part of the file header record. For example: 121140399.

Data element that is part of the file header record. For example: 1456726789.

Data element that is part of the file header record. For example: SILICON VALLEY BANK.

Data element that is part of the file header record. For example: PEACH FINANCE INC.

Data element that is part of the batch header record. For example: PEACH FIN ACH.

Data element that is part of the batch header record. For example: 2837461011.

Data element that is part of the batch header record. For example: 12773923.

If the value is NOT provided (aka null or empty) as part of the configuration, the system will automatically set this value to achFileHeaderImmediateDestination without the last digits. For example: if achFileHeaderImmediateDestination=121140399, the system will set achBatchHeaderOriginatingDFIId=12114039.

How the fee is charged by the payment processor. If the full amount is transferred, and fees are charged monthly, use gross. If fees are deducted from the amount transferred, use net.

The fee charged by the payment processor for regular ACH transactions. For example: 0.05

The fee charged by the payment processor for same day ACH transactions. For example: 0.50

The Standard Entry Class Code within ACH.

The hostname for SFTP. Host name should not contain a scheme, so don't put sftp:// on the front. You may optionally specify a port like so: example.com:222. If no port is supplied a default of 22 will be used.

The method used to access the sftpHostname.

• If usernamePassword, then sftpUsername and sftpPassword must be provided.
• If keys, then sftpSSHPeachPrivateKey and sftpSSHPeachPublicKey will be created by peach.

The username for SFTP.

The password for SFTP.

A json object of any algorithms that need to be disabled when accessing sftpHostname with a private key. This should be null in most scenarios.

The folder where files (e.g. ACH instructions) will be uploaded. The system will change directory into this folder before performing the upload.

The folder where files (e.g. ACH returns) will be downloaded from. The system will change directory into this folder before performing the download.

The name of the ACH confirmation file. The format is a regular expression. If you are not sure how to set up the regular expression, please contact the Peach team by providing a few examples of file names.

If the value is not provided, we assume that the processor doesn't support ACH confirmation files and any upload of an ACH file is considered as successful.

The name of the ACH return file. The format is a regular expression. If you are not sure how to set up the regular expression, please contact the Peach team by providing a few examples of file names.

• If true, files (e.g. ACH) will be named based on the ACHP_MMDDYYYYHHMM convention. For example: ACHP_110320211305.
• If false, files (e.g. ACH) will be named based on a custom implementation. Do not set false unless you’ve coordinated with the Peach team.

• If true, outgoing files will be encrypted with thirdPartyPublicKey and signed with peach's private key. Make sure to set encryptionMethodOutgoing and thirdPartyPublicKey values.
• If false, outgoing files will not be signed with peach's private key.

The encryption method that Peach system will use to encrypt the outgoing files from Peach. Keep the value empty if no encryption is needed. If encryptionMethodOutgoing is set, a value must be set for thirdPartyPublicKey.

The encryption method that Peach system will use to decrypt the incoming files to Peach. Make sure you use peachPublicKey to encrypt the files sent to Peach or uploaded to SFTP for Peach. Keep the value empty if no encryption is needed.