Unified Money Movement Services for Financial Institutions (1.0)

Contact/customers: support@billerpayments.com License: © Alacriti Inc

Transfers & Payments


This API facilitates account-to-account transfers and related functionalities for SMB, Commercial, Corporate and other business customers of banks and credit unions.

Transfer

Create Simple Transfer

Create Simple Transfer API is used to transfer funds from a customer's bank account to another bank account or debit card without explicitly adding a beneficiary or beneficiary account. This is useful when the customer wants to make a one-off payment to an account.

postretailbanking/simplepayment
https://api.orbipay.com/fasterpayments/v1retailbanking/simplepayment
query Parameters
name_match
string

Indicates card account name match strategy to be followed.

Possible Values :
strict complete name match only.
lenient complete or partial name match, name match not supported for card.
ignore name match not required. default

approval
string

Indicates if approval is required or not before processing the transaction.

Possible Values :
required Approval is required.
not_required Approval is not required. default

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
source
required
object

The source of funds, or debtor.

source_account
required
bank_account (object) or card_account (object)

Indicates source account

original_source
object

The name of the actual payer or the ultimate debtor.

destination
object

The recipient of funds, or creditor.

ultimate_destination
object

The actual recipient of funds or the ultimate creditor. This could be different from the entity whose account is being credited.

destination_account
bank_account (object) or card_account (object) or xb_bank_account (object)

Indicates the recipient account of the payment.

Constraints: CMM23
intermediary_agent
Array of objects

Intermediary Agent

amount
required
object

The amount being transfered from the source account to the destination account.

fee
object

The fee being charged for the transfer being made.

payment_reference
required
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

end_to_end_reference
required
string [ 1 .. 35 ] characters

The reference for the payment that is passed on from the initiator to the recipient. This is the reference that traces the entire flow of the payment. However, please note that certain payment rails do not support an end to end reference.The maximum length for the end_to_end_reference varies across different payment rails and is outlined below

Payment Method Max Length Sent to Network
RTP 35 Yes
FEDNOW 35 Yes
FEDWIRE 35 Yes
ACH 15 Yes
CARD_VISA 16 No

uetr
string [ 1 .. 36 ] characters [a-f0-9]{8}-[a-f0-9]{4}-4[a-f0-9]{3}-[89ab][a-f0-9]{3}-[a-f0-9]{12}

The Universally unique identifier that the bank might want to assign a unique end-to-end reference of a payment transaction.

fulfilment_type
string
Enum: "instant" "regular" "instant.BOOK_TRANSFER" "instant.TCH_RTP" "instant.FEDNOW" "instant.CARD_VISA" "urgent.SAMEDAY_ACH" "urgent.FEDWIRE" "regular.ACH"
payment_date
string 10 characters YYYY-MM-DD
businessfunction_entryclass
VISA (string) or NACHA (string) or FEDWIRE (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions, the Standard Entry Class (SEC) code in the case of ACH transactions and so on.

purpose
object

Underlying reason for the payment transaction. Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

payment_category
object

Specifies the high level purpose of the instruction based on a set of pre-defined categories. This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain.

Constraints: CMM16
instruction_for_fi
Array of objects
remittance_info
object

Information supplied to enable the matching/reconciliation of an entry with the item(s) that the payout is intended to settle, such as bills or RFPs received.

related_remittance_info
object
approval_info
Array of objects

Information about who has created and approved the payment.

Responses

201

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.payment.payment_originated
moneymovementservices.payment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

Update Transfer

The Update Transfer API is used to modify details of an existing fund transfer initiated through the Simple Transfer API. This allows customers to make adjustments to a previously created transfer, such as changing the transfer amount, schedule date, or recipient details, before the transfer is executed. The Edit Transfer API is particularly useful for correcting errors or updating information for a one-off payment without the need to reinitiate the transfer.

post/transfer/updatetransfer
https://api.orbipay.com/fasterpayments/v1/transfer/updatetransfer
query Parameters
name_match
string

Indicates card account name match strategy to be followed.

Possible Values :
strict complete name match only.
lenient complete or partial name match, name match not supported for card.
ignore name match not required. default

approval
string

Indicates if approval is required or not before processing the transaction.

Possible Values :
required Approval is required.
not_required Approval is not required. default

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:c_session_id=SADKAS2131312;c_ip=10.112.25.45

Request Body Schema: application/json
payment_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank had assigned when the payment was initially created.This identifier is required to locate the existing payment record and make the necessary edits.

Constraints: CMM11
id
string [ 0 .. 20 ] characters [0-9]{1,20}

The unique identifier assigned by Unified Money Movement Services to payment was originally created.

Constraints: CMM11
original_source
object

The name of the actual payer or the ultimate debtor.

source_account
required
bank_account (object) or card_account (object)

Indicates source account

destination
object

The recipient of funds, or creditor.

ultimate_destination
object

The actual recipient of funds or the ultimate creditor. This could be different from the entity whose account is being credited.

destination_account
required
bank_account (object) or card_account (object) or xb_bank_account (object)

Indicates the recipient account of the payment.

intermediary_agent
Array of objects

Intermediary Agent

amount
required
object

The amount being transfered from the source account to the destination account.

fee
object

The fee being charged for the transfer being made.

payment_date
string 10 characters YYYY-MM-DD
businessfunction_entryclass
VISA (string) or NACHA (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions, the Standard Entry Class (SEC) code in the case of ACH transactions and so on.

purpose
object

Underlying reason for the payment transaction. Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

payment_category
object

Specifies the high level purpose of the instruction based on a set of pre-defined categories. This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain.

Constraints: CMM16
instruction_for_fi
Array of objects
remittance_info
object

Information supplied to enable the matching/reconciliation of an entry with the item(s) that the payout is intended to settle, such as bills or RFPs received.

related_remittance_info
object
approval_info
Array of objects

Information about who has created and approved the payment.

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.payment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

Prepare Transfer

Prepare Transfer API is used to validate and review transfer requests before initiating the actual fund transfer request from a customer's bank account to another bank account or debit card without explicitly adding a beneficiary or beneficiary account. This is useful when the customer wants to make a one-off payment to an account.

post/transfer/preparetransfer
https://api.orbipay.com/fasterpayments/v1/transfer/preparetransfer
query Parameters
name_match
string

Indicates card account name match strategy to be followed.

Possible Values :
strict complete name match only.
lenient complete or partial name match, name match not supported for card.
ignore name match not required. default

approval
string

Indicates if approval is required or not before processing the transaction.

Possible Values :
required Approval is required.
not_required Approval is not required. default

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
source
required
object

The source of funds, or debtor.

source_account
required
bank_account (object) or card_account (object)

Indicates source account

original_source
object

The name of the actual payer or the ultimate debtor.

destination
object

The recipient of funds , or creditor .

ultimate_destination
object

The actual recipient of funds or the ultimate creditor. This could be different from the entity whose account is being credited.

destination_account
required
bank_account (object) or card_account (object)

Indicates the recipient account of the payment.

intermediary_agent
Array of objects

Intermediary Agent

amount
required
object

The amount being transfered from the source account to the destination account.

payment_reference
required
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

end_to_end_reference
required
string [ 1 .. 35 ] characters

The reference for the payment that is passed on from the initiator to the recipient. This is the reference that traces the entire flow of the payment. However, please note that certain payment rails do not support an end to end reference.The maximum length for the end_to_end_reference varies across different payment rails and is outlined below

Payment Method Max Length Sent to Network
RTP 35 Yes
FEDNOW 35 Yes
FEDWIRE 35 Yes
ACH 15 Yes
CARD_VISA 16 No

fulfilment_type
string
Enum: "instant" "regular" "instant.BOOK_TRANSFER" "instant.TCH_RTP" "instant.FEDNOW" "instant.CARD_VISA" "urgent.SAMEDAY_ACH" "urgent.FEDWIRE" "regular.ACH"
payment_date
string 10 characters YYYY-MM-DD
businessfunction_entryclass
VISA (string) or NACHA (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions, the Standard Entry Class (SEC) code in the case of ACH transactions and so on.

purpose
object

Underlying reason for the payment transaction. Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

instruction_for_fi
Array of objects
remittance_info
object

Information supplied to enable the matching/reconciliation of an entry with the item(s) that the payout is intended to settle, such as bills or RFPs received.

related_remittance_info
object

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

+

Request Payload Sample

+

Response Payload Sample

Cancel Payment

Cancel Payment Api will cancel the scheduled payments.

post/cancel/cancelpayment
https://api.orbipay.com/fasterpayments/v1/cancel/cancelpayment
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
payment_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

Constraints: CMM11
id
string

The unique identifier assigned by Unified Money Movement Services to payment.

Constraints: CMM11
notes
string

memo or comment.

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.payment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

Recurring Transfer

Create Recurring Transfer

post/transfer/recurringtransfer
https://api.orbipay.com/fasterpayments/v1/transfer/recurringtransfer
query Parameters
name_match
string

Indicates card account name match strategy to be followed.

Possible Values :
strict complete name match only.
lenient complete or partial name match, name match not supported for card.
ignore name match not required. default

approval
string

Indicates if approval is required or not before processing the transaction.

Possible Values :
required Approval is required.
not_required Approval is not required. default

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
source
required
object

The source of funds, or debtor.

source_account
required
bank_account (object) or card_account (object)

Indicates source account

original_source
object

The name of the actual payer or the ultimate debtor.

destination
object

The recipient of funds , or creditor.

ultimate_destination
object

The actual recipient of funds or the ultimate creditor. This could be different from the entity whose account is being credited.

destination_account
required
bank_account (object) or card_account (object)

Indicates the recipient account of the payment.

intermediary_agent
Array of objects

Intermediary Agent

amount
required
object

The amount being transfered from the source account to the destination account.

fee
object

The fee being charged for the transfer being made.

payment_setup_reference
required
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

end_to_end_reference
required
string [ 1 .. 35 ] characters

The reference for the payment that is passed on from the initiator to the recipient. This is the reference that traces the entire flow of the payment. However, please note that certain payment rails do not support an end to end reference.The maximum length for the end_to_end_reference varies across different payment rails and is outlined below

Payment Method Max Length Sent to Network
RTP 35 Yes
FEDNOW 35 Yes
FEDWIRE 35 Yes
ACH 15 Yes
CARD_VISA 16 No

fulfilment_type
required
string
Enum: "urgent.ACH" "urgent.FEDWIRE" "regular.ACH"
payment_date
string 10 characters YYYY-MM-DD
businessfunction_entryclass
VISA (string) or NACHA (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions, the Standard Entry Class (SEC) code in the case of ACH transactions and so on.

purpose
object

Underlying reason for the payment transaction. Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

instruction_for_fi
Array of objects
remittance_info
object

Information supplied to enable the matching/reconciliation of an entry with the item(s) that the payout is intended to settle, such as bills or RFPs received.

related_remittance_info
object
frequency
required
string
Enum: "daily" "weekly" "biweekly" "monthly" "quarterly" "yearly"
number_of_occurrences
string [0-9]{1,20}

It specifies the number of payments to be done.

Constraints: CMM15
start_date
required
string ^[0-9]{4}-(0?[1-9]|1[0-2])-(0?[1-9]|1\d|2\d|3[01])$

The date on which the first payment will be drafted as part of a recurring payment setup. This is to be specified in the ISO8601 full-date format, namely, YYYY-MM-DD.

end_date
string ^[0-9]{4}-(0?[1-9]|1[0-2])-(0?[1-9]|1\d|2\d|3[01])$

The date by which the last payment will be drafted as part of a recurring payment setup. This is to be specified in the ISO8601 full-date format, namely, YYYY-MM-DD.

Constraints: CMM15
approval_info
Array of objects

Information about who has created and approved the payment.

Responses

201

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Events

Following events are triggered in the context of this API
moneymovementservices.recurringpayment.payment_scheduled

+

Request Payload Sample

+

Response Payload Sample

Get Recurring Transfer

post/transfer/getrecurringtransfer
https://api.orbipay.com/fasterpayments/v1/transfer/getrecurringtransfer
header Parameters
product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
payment_setup_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

Constraints: CMM11
id
string

The unique identifier assigned by Unified Money Movement Services to payment.

Constraints: CMM11

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

+

Request Payload Sample

+

Response Payload Sample

Get Recurring Transfer Instances

post/transfer/getrecurringinstances
https://api.orbipay.com/fasterpayments/v1/transfer/getrecurringinstances
header Parameters
product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
payment_setup_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

Constraints: CMM11
id
string

The unique identifier assigned by Unified Money Movement Services to payment.

Constraints: CMM11
from_date
string

The instances generated after the date provided.

to_date
string

The instances generated before the date provided..

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

+

Request Payload Sample

+

Response Payload Sample

Delete Recurring Transfer

post/transfer/deleterecurringtransfer
https://api.orbipay.com/fasterpayments/v1/transfer/deleterecurringtransfer
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
payment_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the recurring payment setup.

Constraints: CMM11
id
string

The unique identifier assigned by Unified Money Movement Services to recurring payment setup.

Constraints: CMM11
memo
string [ 1 .. 200 ] characters

The memo to delete the recurring payment setup.

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

+

Request Payload Sample

+

Response Payload Sample

ACH Mass Payment

Inquire Batch Payment

Create Batch Payment API is used to make multiple payments in a batch mode. A batch can contain a list of either transfers or payouts. All payments in the batch should have the same payment date. If its batch is a payout batch, all the payments should have the same source.

post/masspayment/inquirebatch
https://api.orbipay.com/fasterpayments/v1/masspayment/inquirebatch
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
batch_reference
required
string [ 1 .. 50 ] characters

The unique identifier that the bank might want to assign for the batch.

file_reference
string [ 1 .. 50 ] characters

The file reference for the batch.

total_txn_count
string [ 1 .. 50 ] characters

Total transaction count in the batch.

total_txn_amount
string [ 1 .. 50 ] characters

Total transaction amount in the batch.

requested_execution_date
string

Requested Execution date.

fulfilment_type
string
Enum: "regular.ACH" "urgent.SAMEDAY_ACH"


regular.ACH - Typically 1-2 business days for processing. default
urgent.SAMEDAY_ACH - Typically same day processing.

payment_category
object

Specifies the high level purpose of the instruction based on a set of pre-defined categories. This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain.

Constraints: CMM16
businessfunction_entryclass
NACHA (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions, the Standard Entry Class (SEC) code in the case of ACH transactions and so on.

Constraints: CMM10
batch_type
required
string
Enum: "debit_batch" "credit_batch"
payment_info
credit_batch (object) or debit_batch (object)

Responses

201

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.batch.status_updated

+

Request Payload Sample

+

Response Payload Sample

Submit Credit Batch

|

post/masspayment/submitcreditbatch
https://api.orbipay.com/fasterpayments/v1/masspayment/submitcreditbatch
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
batch_info
object
credit_batch
Array of objects

Responses

200

The request has succeeded.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.batch.status_updated

+

Request Payload Sample

+

Response Payload Sample

Submit Debit Batch

|

post/masspayment/submitdebitbatch
https://api.orbipay.com/fasterpayments/v1/masspayment/submitdebitbatch
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
batch_info
object
debit_batch
Array of objects

Responses

200

The request has succeeded..

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.batch.status_updated

+

Request Payload Sample

+

Response Payload Sample

Confirm Batch

|

post/masspayment/confirmbatch
https://api.orbipay.com/fasterpayments/v1/masspayment/confirmbatch
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
id
string [ 1 .. 50 ] characters
batch_reference
required
string [ 1 .. 50 ] characters

The unique identifier that the bank might want to assign for the batch.

requested_execution_date
string

Requested Execution date.

Responses

200

The Batch object with id issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.batch.status_updated

+

Request Payload Sample

+

Response Payload Sample

Cancel Batch

This API is used to cancel the Batch.

post/masspayment/cancelbatch
https://api.orbipay.com/fasterpayments/v1/masspayment/cancelbatch
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party, client_agent, external_agent

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
id
string [ 1 .. 50 ] characters
batch_reference
required
string [ 1 .. 50 ] characters

The unique identifier that the bank might want to assign for the batch.

Responses

200

The Batch object with id issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Events

Following events are triggered in the context of this API
moneymovementservices.batch.status_updated

+

Request Payload Sample

+

Response Payload Sample

XB Transfer

Prepare XB Transfer

Create Simple XB Transfer API is used to transfer funds from a customer's bank account to another bank account cross broder without explicitly adding a beneficiary or beneficiary account. This is useful when the customer wants to make a one-off payment to an account.

post/xbtransfer/preparetransfer
https://api.orbipay.com/fasterpayments/v1/xbtransfer/preparetransfer
header Parameters
client_key
required
any

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
any

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
any

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
any

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
any

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
any

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
any

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
any

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
any

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
any

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
any

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
source
required
object

The source of funds, or debtor.

source_account
required
bank_account (object)

Indicates source account

destination
required
object

The recipient of funds , or creditor .

destination_account
required
xb_bank_account (object)

Indicates the recipient account of the payment.

fulfilment_type
required
string
Enum: "xb.wire" "xb.wire.convera"
amount
required
object

The amount being transfered from the source account to the destination account.

fee
object

The fee being charged for the transfer being made.

payment_reference
required
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

end_to_end_reference
required
string [ 1 .. 35 ] characters

The reference for the payment that is passed on from the initiator to the recipient. This is the reference that traces the entire flow of the payment. However, please note that certain payment rails do not support an end to end reference.The maximum length for the end_to_end_reference varies across different payment rails and is outlined below

Payment Method Max Length Sent to Network
RTP 35 Yes
FEDNOW 35 Yes
FEDWIRE 35 Yes
ACH 15 Yes
CARD_VISA 16 No

uetr
string

The unique transaction identifier.

remittance_info
object

Information supplied to enable the matching/reconciliation of an entry with the item(s) that the payout is intended to settle, such as bills or RFPs received.

purpose
object

Underlying reason for the payment transaction. Purpose is used by the end-customers, that is initiating party, (ultimate) debtor, (ultimate) creditor to provide information concerning the nature of the payment. Purpose is a content element, which is not used for processing by any of the agents involved in the payment chain.

instruction_for_fi
Array of objects
approval_info
Array of objects

Information about who has created and approved the payment.

payment_category
object

Specifies the high level purpose of the instruction based on a set of pre-defined categories. This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain.

Constraints: CMM16
intermediary_agent
Array of objects

Intermediary Agent

Responses

201

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.xbpayment.payment_originated
moneymovementservices.xbpayment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

Perform XB Transfer

Perform XB payment.

post/xbtransfer/performtransfer
https://api.orbipay.com/fasterpayments/v1/xbtransfer/performtransfer
query Parameters
approval
string

Indicates if approval is required or not before processing the transaction.

Possible Values :
required Approval is required.
not_required Approval is not required. default

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
payment_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

Constraints: CMM11
id
string

The unique identifier assigned by Unified Money Movement Services to payment.

Constraints: CMM11

Responses

201

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

412

The Payment object with id returned by Unified Money Movement Services when precondition fails.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.xbpayment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

Cancel XB Transfer

Cancel XB payemnt.

post/xbtransfer/canceltransfer
https://api.orbipay.com/fasterpayments/v1/xbtransfer/canceltransfer
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
id
string

The unique identifier assigned by Unified Money Movement Services to payment.

Constraints: CMM11
payment_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

Constraints: CMM11
confirmation_number
string [ 1 .. 30 ] characters [a-zA-Z0-9]+

The confirmation number or reference provided to the customer for the payment.

comment
string [ 1 .. 140 ] characters [a-zA-Z0-9]+

The reason for cancelling the transfer.

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

Events

Following events are triggered in the context of this API
moneymovementservices.xbpayment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

RFP

Send RFP

post/request/sendrfp
https://api.orbipay.com/fasterpayments/v1/request/sendrfp
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

processing_mode
string

Indicates whether the transaction will be processed synchronously or asynchronously, in a non-blocking fashion.

Possible Values :
synchronous The transaction will be processed in a blocking fashion. default
asynchronous The transaction will be processed in a non-blocking fashion.

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:c_session_id=SADKAS2131312;c_ip=10.112.25.45

Request Body Schema: application/json
source
required
object

The recipient of the RFP or Debtor.

source_account
required
object

Indicates the source of funds of the RFP or debtor account.

destination
required
object

The recipient of funds.

destination_account
required
object

The recipient account, where the funds will be credited.

end_to_end_reference
required
string [ 1 .. 35 ] characters [0-9a-zA-Z._\\- ]{0,35}

The reference for the payment that is passed on from the initiator to the recipient. This is the reference that traces the entire flow of the payment. However, please note that certain payment rails do not support an end to end reference.The maximum length for the end_to_end_reference varies across different payment rails and is outlined below

Payment Method Max Length Sent to Network
RTP 35 Yes
FEDNOW 35 Yes
FEDWIRE 16 Yes

fulfilment_type
required
string
Enum: "instant.TCH_RTP" "instant.FEDNOW" "urgent.FEDWIRE"

Specifies the type and speed of payment processing.

Enum values:

  • instant.TCH_RTP: RFP using The Clearing House RTP network.
  • instant.FEDNOW: RFP using the FedNow service.
  • urgent.FEDWIRE: RFP using the Fedwire network.
amount
required
Array of objects

amount

requested_execution_date
required
string [0-9]{4}-[0-9]{2}-[0-9]{2}

The date on which the debtor's account(s) is (are) to be debited.

expiry_date
string [0-9]{4}-[0-9]{2}-[0-9]{2}

The debtor must accept or reject the request by this specified date. After this date, the request becomes void and can no longer be processed; any payments received in response to the RFP will be rejected.
Note: This feature does not apply to Fedwire.

remittance_info
object

Information supplied to enable the matching/reconciliation of an entry with the item(s) that the payout is intended to settle, such as bills or RFPs received.

rfp_reference
required
string [ 1 .. 36 ] characters [0-9a-zA-Z._-]{0,36}

The unique identifier that the bank might want to assign for the RFP.

Responses

200

Success

400

Bad Request

500

System Error.

502

Server Error.

Events

Following events are triggered in the context of this API
moneymovementservices.rfp.rfp_originated
moneymovementservices.rfp.rfp_updated
moneymovementservices.receivedpayment.payment_received
moneymovementservices.receivedpayment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

Cancel RFP

post/request/cancelrfp
https://api.orbipay.com/fasterpayments/v1/request/cancelrfp
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
id
string [ 0 .. 20 ] characters [0-9]{1,20}

The unique identifier assigned to rfp.

Constraints: CMM22
rfp_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z._-]{0,36}

The unique identifier that the client might want to assign for the rfp.

Constraints: CMM22
cancellation_reason
required
object
reject_payment
boolean
Enum: true false

Indicates whether the payment should be rejected if cancellation is not possible.

Responses

200

Success

400

Bad Request

500

System Error.

502

Server Error.

Events

Following events are triggered in the context of this API
moneymovementservices.rfp.rfp_updated

+

Request Payload Sample

+

Response Payload Sample

Accept / Reject RFP

The API is used to accept or reject an RFP received earlier. This is, in turn, communicated to the sender of the RFP (creditor). Accepting an RFP does not automatically originate a credit transfer against the RFP. This will have to be initiated explicitly per the terms of the RFP that have been accepted.

post/request/{rfp_id}/review
https://api.orbipay.com/fasterpayments/v1/request/{rfp_id}/review
path Parameters
rfp_id
required
string

The reference of the RFP received that is being accepted or rejected.

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:smb_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
action
required
string
Enum: "accepted" "rejected"

Indicates if the RFP is being accepted or rejected.

comment
string [ 1 .. 100 ] characters [0-9a-zA-Z._-]{0,100}

Customer’s comments or memo on the RFP being accepted or rejected.

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Events

Following events are triggered in the context of this API
moneymovementservices.receivedrfp.rfp_updated
moneymovementservices.payment.payment_originated
moneymovementservices.payment.payment_updated

+

Request Payload Sample

+

Response Payload Sample

Status

Get Payment Status

Get Payment Status API returns the current status of payment.

post/status/getpaymentstatus
https://api.orbipay.com/fasterpayments/v1/status/getpaymentstatus
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
payment_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the payment.

Constraints: CMM11
id
string

The unique identifier assigned by Unified Money Movement Services to payment.

Constraints: CMM11

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

+

Request Payload Sample

+

Response Payload Sample

Get RFP Status

Get RFP Status API returns the current status of RFP.

post/status/getrfpstatus
https://api.orbipay.com/fasterpayments/v1/status/getrfpstatus
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
rfp_reference
string [ 1 .. 36 ] characters [0-9a-zA-Z_-]{1,36}

The unique identifier that the bank might want to assign for the RFP.

Constraints: CMM22
id
string

The unique identifier assigned by Unified Money Movement Services to RFP.

Constraints: CMM22

Responses

200

The Payment object with id and confirmation mumber issued by Unified Money Movement Services.

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

+

Request Payload Sample

+

Response Payload Sample

Ancillary

Get Routing Details

The API provides information about a Routing and Transit Number, including the identified participant in the requested network, the supported network messages, and the current status of the participant FI.

get/route/routingdetails/{routing_number}
https://api.orbipay.com/fasterpayments/v1/route/routingdetails/{routing_number}
path Parameters
routing_number
required
string

Routing number of the participant FI

query Parameters
fulfilment_type
Array of strings
Items Enum: "instant" "regular" "instant.TCH_RTP" "instant.FEDNOW" "urgent.SAMEDAY_ACH" "urgent.FEDWIRE" "regular.ACH"

This should be provided as an input to check the availability of a routing number in a specific payment network. If not provided, the system will, by default, check availability in RTP and FedNow payment networks.

More than one payment network can be provided by passing multiple fulfilment_type parameters in the request, as shown below. Example: fulfilment_type=instant&fulfilment_type=regular&fulfilment_type=urgent.FEDWIRE

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

+

Response Payload Sample

Get Indicative Rate

The API is used to get the current flex rate of the given currency

post/rates/indicativerates
https://api.orbipay.com/fasterpayments/v1/rates/indicativerates
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
send_country
string

send country

send_currency
string

send currency

receive_country
string

receive country

receive_currency
string

receive currency

specified_amount
string

specified amount

specified_currency
string

specified currency

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

+

Request Payload Sample

+

Response Payload Sample

Verify Card Details

The API is used to validate a card for payment.

post/card/verify
https://api.orbipay.com/fasterpayments/v1/card/verify
query Parameters
name_match
string

Indicates card account name match strategy to be followed.

Possible Values :
strict complete name match only.
lenient complete or partial name match, name match not supported for card.
ignore name match not required. default

header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
businessfunction_entryclass
VISA (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions.

card_account
object

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

+

Request Payload Sample

+

Response Payload Sample

Find Bank

The API is used to get bank details. One of the following combinations of parameters is required to search for the bank effectively.

IBAN + IBAN Country Code
Bank Code + Address Country Code
Bank Branch Code + Address Country Code
Address Country Code + City + Bank Name + any other parameters

post/route/bankdetails
https://api.orbipay.com/fasterpayments/v1/route/bankdetails
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
iban
string
iban_country_code
string
bank_code
string
bank_name
string
bank_branch_code
string
address
object

The postal address .

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

+

Request Payload Sample

+

Response Payload Sample

Get Payment Data Fields

The API is used to get the field details required to make the payment.

post/route/getpaymentdatafields
https://api.orbipay.com/fasterpayments/v1/route/getpaymentdatafields
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
destination_bank_country_code
required
string <[A-Z]{2,2}>

The country code of the recipient bank.

currency_code
required
string <[A-Z]{3,3}>

The currency code.

destination_country_code
string <[A-Z]{2,2}>

The country code of the recipient. This can be different from the recipient's bank country.

payment_method
string


Possible Values :- XB_ACH, XB_WIRE

party_type
string

Entity type

Possible Values :
INDIVIDUAL,BUSINESS

fx_provider
string
Enum: "xb.fx.convera" "xb.fx.wellsfargo" "xb.fx.stonex"

Defines which FX provider should be used when fetching payment data fields.

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

+

Request Payload Sample

+

Response Payload Sample

List Supported Corridors

The API is used to get the list of supported corridores.

get/route/supportedcorridors/
https://api.orbipay.com/fasterpayments/v1/route/supportedcorridors/
query Parameters
destination_country_code
string

Country code filter(Ex- GB, IN, US etc..)

payment_method_name
string

Payment method filter.
Example Value :- XB_WIRE, XB_ACH

header Parameters
client_key
required
any

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
any

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
any

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
any

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
any

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
any

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
any

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
any

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
any

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
any

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
any

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

+

Response Payload Sample

Calculate Fee

The API is used to evaluate the fee for a transaction.

post/calculatefee
https://api.orbipay.com/fasterpayments/v1/calculatefee
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:session=SADKAS2131312;ip_address=10.112.25.45

Request Body Schema: application/json
source
required
object

The source of funds, or debtor.

source_account
required
bank_account (object) or card_account (object)

Indicates source account

destination
object

The recipient of funds, or creditor.

destination_account
required
bank_account (object) or card_account (object)

Indicates the recipient account of the payment.

amount
required
object

The amount being transfered from the source account to the destination account.

businessfunction_entryclass
VISA (string) or NACHA (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions, the Standard Entry Class (SEC) code in the case of ACH transactions and so on.

fulfilment_type
required
string
Enum: "instant" "regular" "regular.ACH" "urgent.ACH" "instant.TCH_RTP" "instant.FEDNOW" "urgent.FEDWIRE" "xb.wire"

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

+

Request Payload Sample

+

Response Payload Sample

Fetch Fee

This API fetches the applicable fees based on the provided details across multiple supported payment rails.

post/fetchfee
https://api.orbipay.com/fasterpayments/v1/fetchfee
header Parameters
client_key
required
string

The unique identifier assigned to the client.
Example:CLIAAADDD0910

product
required
string

The product identifier corresponding to the API.
Possible values:retail_transfers,smb_transfers ,commercial_transfers

payment_channel
required
string

The FI channel vide which the API is invoked.
Possible values:retail_banking,business_banking, bank_bos, atm, kiosk, pos, mobile_banking, csm, online

access_channel
string

This is internal channel through which the API is invoked.
Example:web_portal, agent

requestor_type
required
string

Identifies the requestor type for the API request.
Possible values:party

client_requestor_reference
string

The identifier for the requestor of the API, in the client system. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

requestor
string

The identifier for the requestor of the API issued by Orbipay. Either the client_requestor_reference or the requestor has to be available in every API request for audit purposes.

context_variant
string

To be used if there's a need to provide additional contextual information. For future use.

idempotent_request_key
required
string

The unique token that clients can generate and maintain in order to identify an API request. This is used to identify duplicate requests and retrials.
Example:6bc5f0f49ee2412a93b0596d6a3c4eca

timestamp
required
string

The UTC datetime when the API is invoked, in the ISO 8601 format
Example:2020-09-18T17:31:34.000-05:30

X-PAAS-Headers
string

For additional context information such as end user IP address, session information and so on. The content is a list of key-value pairs separated by semicolon (;) where key and value are separated by equals sign(=).
Example:c_session_id=SADKAS2131312;c_ip=10.112.25.45

Request Body Schema: application/json
source
object

The source of funds, or debtor.

source_account
required
bank_account (object) or card_account (object)

Indicates source account

destination
object

The recipient of funds, or creditor.

destination_account
required
bank_account (object) or card_account (object)

Indicates the recipient account of the payment.

amount
required
object

The amount being transfered from the source account to the destination account.

businessfunction_entryclass
VISA (string) or NACHA (string)

The payment network specific code corresponding to the business application or function for the transaction. This corresponds to the Business Application Identifier (BAI) in the case of Visa transactions, the Standard Entry Class (SEC) code in the case of ACH transactions and so on.

fulfilment_type
required
Array of strings

A list of fulfillment types can be provided to assess the applicable fees.
Possible values:- instant, regular, regular.ACH, urgent.ACH, instant.TCH_RTP, instant.FEDNOW, urgent.FEDWIRE, xb.WIRE, xb.ACH.

Responses

200

Success

400

Bad Request

401

Unauthorized

403

Forbidden

404

The requested resource doesn't exist.

422

The parameters were valid but the request failed.

500

Something went wrong and the request could not be processed.

502

Server Error.

Error Codes

The following table lists the business errors that need to be handled by the client.
click here

+

Request Payload Sample

+

Response Payload Sample