Action Payment

patch

https://server:port/spl/rest/apis/customer/financials/payments/{paymentId}/action

This operation handles the Integration Suite API to Action Payment

Request

Path Parameters
Query Parameters
Supported Media Types
Request Body - application/xml ()
Root Schema : schema
Type: object
Show Source
  • Maximum Length: 30
    If the payment is canceled , the Cancel Reason is displayed.
    Example: Data entry error
  • When Payment Transfer button is clicked, the Payment Event Transfer dialog opens to transfer a payment.
    Example: true
  • (name)
  • nextActions
  • Maximum Length: 12
    Payment ID is the system-assigned unique identifier of the payment.
    Example: 317896608844
  • Allowed Values: [ "10 ", "20 ", "30 ", "50 ", "60 " ]
    Payment Status is the payment's status. * `10 ` - Incomplete, * `20 ` - Error, * `30 ` - Freezable, * `50 ` - Frozen, * `60 ` - Canceled
    Example: 30
  • Maximum Length: 10
    Account ID is the account to which the payment event should be transferred.
  • Maximum Length: 4
    Cancel Reason defines why you are performing the payment event transfer.
    Example: NSF (Non sufficient funds)
  • Maximum Length: 8
    Match Type and Match Value are defaulted based on their values for the payment event that you are transferring. If necessary, modify the values appropriately for the account to which you are transferring the payment event.
    Example: BILL-ID (Bill ID / Sequential Bill Number)
  • Maximum Length: 30
    Match Type and Match Value are defaulted based on their values for the payment event that you are transferring. If necessary, modify the values appropriately for the account to which you are transferring the payment event.
    Example: 995516242555
  • Maximum Length: 254
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
  • Maximum Length: 50
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
  • Maximum Length: 30
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
Nested Schema : nextActions
Type: object
Show Source
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Maximum Length: 30
    If the payment is canceled , the Cancel Reason is displayed.
    Example: Data entry error
  • When Payment Transfer button is clicked, the Payment Event Transfer dialog opens to transfer a payment.
    Example: true
  • (name)
  • nextActions
  • Maximum Length: 12
    Payment ID is the system-assigned unique identifier of the payment.
    Example: 317896608844
  • Allowed Values: [ "10 ", "20 ", "30 ", "50 ", "60 " ]
    Payment Status is the payment's status. * `10 ` - Incomplete, * `20 ` - Error, * `30 ` - Freezable, * `50 ` - Frozen, * `60 ` - Canceled
    Example: 30
  • Maximum Length: 10
    Account ID is the account to which the payment event should be transferred.
  • Maximum Length: 4
    Cancel Reason defines why you are performing the payment event transfer.
    Example: NSF (Non sufficient funds)
  • Maximum Length: 8
    Match Type and Match Value are defaulted based on their values for the payment event that you are transferring. If necessary, modify the values appropriately for the account to which you are transferring the payment event.
    Example: BILL-ID (Bill ID / Sequential Bill Number)
  • Maximum Length: 30
    Match Type and Match Value are defaulted based on their values for the payment event that you are transferring. If necessary, modify the values appropriately for the account to which you are transferring the payment event.
    Example: 995516242555
  • Maximum Length: 254
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
  • Maximum Length: 50
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
  • Maximum Length: 30
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
Nested Schema : nextActions
Type: object
Show Source
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
Back to Top

Response

Supported Media Types

200 Response

Success response
Body ()
Root Schema : C1ActionPyt
Type: object
Show Source
  • Maximum Length: 30
    If the payment is canceled , the Cancel Reason is displayed.
    Example: Data entry error
  • When Payment Transfer button is clicked, the Payment Event Transfer dialog opens to transfer a payment.
    Example: true
  • (name)
  • nextActions
  • Maximum Length: 12
    Payment ID is the system-assigned unique identifier of the payment.
    Example: 317896608844
  • Allowed Values: [ "10 ", "20 ", "30 ", "50 ", "60 " ]
    Payment Status is the payment's status. * `10 ` - Incomplete, * `20 ` - Error, * `30 ` - Freezable, * `50 ` - Frozen, * `60 ` - Canceled
    Example: 30
  • Maximum Length: 10
    Account ID is the account to which the payment event should be transferred.
  • Maximum Length: 4
    Cancel Reason defines why you are performing the payment event transfer.
    Example: NSF (Non sufficient funds)
  • Maximum Length: 8
    Match Type and Match Value are defaulted based on their values for the payment event that you are transferring. If necessary, modify the values appropriately for the account to which you are transferring the payment event.
    Example: BILL-ID (Bill ID / Sequential Bill Number)
  • Maximum Length: 30
    Match Type and Match Value are defaulted based on their values for the payment event that you are transferring. If necessary, modify the values appropriately for the account to which you are transferring the payment event.
    Example: 995516242555
  • Maximum Length: 254
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
  • Maximum Length: 50
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
  • Maximum Length: 30
    Following parameters must be specified in the Payment Event Transfer dialog to transfer a payment - Non CIS Name, Reference Number, and Non CIS Comments. Non CIS Name, Reference Number, and Non CIS Comments appear if the Account ID belongs to a customer class that is used for non-CIS payments.
Nested Schema : nextActions
Type: object
Show Source
Nested Schema : _data
Type: array
Show Source
Nested Schema : items
Type: object
Show Source

400 Response

Bad Request
Body ()
Root Schema : problemDetailDocument
Type: object
Show Source
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 9999
    The HTTP Status code for the error.
  • Maximum Length: 60
    Fully qualified URL consisting of the Base URI Timestamp of error in ISO format, the User used for the transaction, the Message Category within Oracle Utilities Application Framework, the Message Number within Oracle Utilities Application Framework, the Request URL and the HTTP method used for the transaction.
  • Maximum Length: 60
    URL of the format "A/message/X/Y" where A is the base URI, X is the Message Category and Y is the Message Number within Oracle Utilities Application Framework.
  • serverMessage
  • Maximum Length: 60
    The stack trace shows where the error occurs during the execution of a program.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
Nested Schema : serverMessage
Type: object
Show Source
  • Maximum Length: 60
    Delimited sequence of programs called.
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 0
    Message Category within Oracle Utilities Application Framework.
  • Minimum Value: -99999
    Maximum Value: 99999
    Message Number within Oracle Utilities Application Framework.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
  • Maximum Length: 60
    Name of the program that encountered the error.

500 Response

Internal Server Error
Body ()
Root Schema : problemDetailDocument
Type: object
Show Source
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 9999
    The HTTP Status code for the error.
  • Maximum Length: 60
    Fully qualified URL consisting of the Base URI Timestamp of error in ISO format, the User used for the transaction, the Message Category within Oracle Utilities Application Framework, the Message Number within Oracle Utilities Application Framework, the Request URL and the HTTP method used for the transaction.
  • Maximum Length: 60
    URL of the format "A/message/X/Y" where A is the base URI, X is the Message Category and Y is the Message Number within Oracle Utilities Application Framework.
  • serverMessage
  • Maximum Length: 60
    The stack trace shows where the error occurs during the execution of a program.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
Nested Schema : serverMessage
Type: object
Show Source
  • Maximum Length: 60
    Delimited sequence of programs called.
  • Maximum Length: 60
    The long message description from the Oracle Utilities Application Framework in CDATA format.
  • Minimum Value: 0
    Maximum Value: 0
    Message Category within Oracle Utilities Application Framework.
  • Minimum Value: -99999
    Maximum Value: 99999
    Message Number within Oracle Utilities Application Framework.
  • Maximum Length: 60
    Fully qualified error message from Oracle Utilities Application Framework in CDATA format.
  • Maximum Length: 60
    Name of the program that encountered the error.
Back to Top