Settlement report Chase Orbital mapping

This integration is currently in beta and the exact mapping of fields might still change.

First, contact the Chase Orbital representative to enable Delimited File Reports (DFR) with the following considerations:

The report must be delivered via SFTP.
ACT0010 Deposit Detail Financial Report needs to be enabled.

After SFTP access has been set up, SFTP credentials are received from Chase Orbital. These credentials are used when enabling settlement reporting in the Chase Orbital connector configuration in the dashboard. To set up these credentials, please go to the “Connections” tab, select the Chase Orbital connector and navigate to the “Settlement” tab. Here settlement reporting can be enabled, after which prompts are provided to fill out the following:

The SFTP username.
The SFTP password.
The SFTP address, which should include a port number. If it is not provided, the port number is defaulted to 22.

Below is the mapping of Chase Orbital’s report to the settlement report. This data is pulled from Chase Orbital’s Delimited File Report (DFR).

Settlement report	Chase Orbital field?	Chase Orbital report
`payment_service_transaction_reconciliation_id`	Yes	`Merchant Order #` (only for `settlement`)
`transaction_id`	No	-
`payment_service_transaction_id`	Yes	Always `null`
`payment_service_id`	No	-
`payment_service_definition_id`	No	-
`payment_service_display_name`	No	-
`journal_type`	Yes	Check journal type mapping table below
`raw_journal_type`	Yes	`Record Type \| Action Code`
`payment_service_transaction_created_at`	Yes	Always `null`
`posted_at`	Yes	`Report Generation Date` + 12 hours
`processing_amount_plain`	Yes	Always `null`
`processing_currency`	Yes	Always `null`
`exchange_rate`	Yes	Always `null`
`currency`	Yes	Standardized value of `Presentment Currency`
`gross_credit_plain`	Yes	`Amount` for `settlement`, `0` otherwise
`net_credit_plain`	Yes	`Amount` for `settlement`, `0` otherwise
`gross_debit_plain`	Yes	`(-1) * Amount` for `refund`, `0` otherwise
`net_debit_plain`	Yes	`(-1) * Amount` for `refund`, `0` otherwise
`fee_markup_plain`	Yes	Always `null`
`fee_interchange_plain`	Yes	Always `null`
`fee_scheme_plain`	Yes	Always `null`
`fee_total_plain`	Yes	Always `0`
`method`	Yes	Standardized value of `MOP`
`raw_method`	Yes	`MOP`
`scheme`	Yes	Standardized value of `MOP`
`raw_scheme`	Yes	`MOP` for card transactions, `null` otherwise
`batch`	Yes	Always `null`
`report_id`	No	-
`raw_report_ids`	No	-
`ingested_at`	No	-
`description`	Yes	Always `null`
`transaction_external_identifier`	No	-
`transaction_metadata`	No	-
`report_payment_service_id`	No	-
`report_payment_service_definition_id`	No	-
`report_payment_service_display_name`	No	-
`payment_service_modification_reference`	Yes	Always `null`
`payment_service_refund_reconciliation_id`	Yes	`Merchant Order #` (only for `refund`)

Notes

The posted_at value provided is an approximation, as the original report does not report this value with a time part.

Journal type mapping

Chase Orbital raw journal type	Journal type
`RACT0010 \| DP`	`settlement`
`RACT0010 \| RF`	`refund`
any other value	`other`

Fields marked as not a Chase Orbital field are populated from internal data and not from the imported payment service report.

Overview

Insights

Monitoring & Alerting

Flow

Roles & Permissions

Reports

Settlement reports

SSO

Settlement report Chase Orbital mapping

Notes

Journal type mapping

​Notes

​Journal type mapping

Notes

Journal type mapping