Get a digital payment account assignment

get

/fscmRestApi/resources/11.13.18.05/paymentsExternalPayees/{PayeeId}/child/digitalPaymentAccountAssignments/{digitalPaymentAccountAssignmentsUniqID}

Request

Path Parameters
  • Application-generated identifier of the external payee.
  • This is the hash key of the attributes which make up the composite key for the Digital Payment Account Assignments resource and used to uniquely identify an instance of Digital Payment Account Assignments. The client should not generate the hash key value. Instead, the client should query on the Digital Payment Account Assignments collection resource in order to navigate to a specific instance of Digital Payment Account Assignments to get the hash key.
Query Parameters
  • This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2

    Format: <attr1>=<val1>,<attr2>=<value2>
  • When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
  • This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.

    Format: ?fields=Attribute1,Attribute2

    Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2
  • This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>

    Example:
    self,canonical
  • The resource item payload will be filtered in order to contain only data (no links section, for example).
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : paymentsExternalPayees-digitalPaymentAccountAssignments-item-response
Type: object
Show Source
  • Title: Account Usage Type
    Read Only: true
    Maximum Length: 80
    Purpose of the digital payment account.
  • Title: Alias
    Maximum Length: 150
    Additional alias used to represent the virtual card digital payment account.
  • Title: Alias
    Maximum Length: 150
    Additional alias used to represent the virtual card digital payment account.
  • Title: Alias
    Maximum Length: 150
    Alias used to represent the digital payment account.
  • Title: Alias
    Maximum Length: 150
    Additional alias used to represent the digital payment account.
  • Title: Alias
    Maximum Length: 150
    Additional alias used to represent the digital payment account.
  • Title: Alias Type
    Read Only: true
    Maximum Length: 80
    Type of alias used to represent the digital payment account.
  • Title: Bank Account
    Maximum Length: 100
    Bank account assigned to the digital payment account.
  • Title: Card Platform
    Read Only: true
    Maximum Length: 80
    Name of the payment system used by the virtual card program.
  • Title: Country Code
    Maximum Length: 2
    Country code of the digital payment account.
  • Title: Created By
    Read Only: true
    Maximum Length: 64
    The user who created the digital payment account assignment.
  • Title: Creation Date
    Read Only: true
    The date and time when the digital payment account assignment was created.
  • Title: Currency Code
    Maximum Length: 15
    Currency code of the digital payment account.
  • Title: Registration Status
    Maximum Length: 80
    Registration status of the provider for the digital payment account.
  • Title: Display Name
    Maximum Length: 150
    Display name of the digital payment account.
  • Title: Digital Payment Account ID
    Unique identifier of the digital payment account.
  • Title: End Date
    The date when the relationship between the payment instrument and the payer or payee becomes inactive in the payment instrument assignment.
  • Title: Inactive On
    The date when the digital payment account expires.
  • Title: Instrument Payment Use ID
    Read Only: true
    Unique identifier of the instrument assignment.
  • Title: Instrument Type
    Read Only: true
    Maximum Length: 80
    Type of payment instrument used in the instrument assignment.
  • Title: Start Date
    Read Only: true
    The date when the digital payment account was issued.
  • Title: Last Updated Date
    Read Only: true
    The date and time when the digital payment account assignment was last updated.
  • Title: Last Updated By
    Read Only: true
    Maximum Length: 64
    The user who last updated the digital payment account assignment.
  • Links
  • Title: Owner Party Name
    Read Only: true
    Maximum Length: 360
    Party name of the digital payment account owner.
  • Title: Owner Party Number
    Read Only: true
    Maximum Length: 30
    Party number of the digital payment account owner.
  • Title: Payment Flow
    Read Only: true
    Maximum Length: 80
    Payment flow that determines whether the instrument assignment is used for outgoing or incoming payments.
  • Title: Payment Mode
    Read Only: true
    Maximum Length: 80
    Payment method used by the digital payment account.
  • Title: Primary
    Maximum Length: 30
    Indicates whether the payment instrument is the primary payment instrument for the payer or payee within the instrument assignment. A primary payment instrument automatically populates the transactions.
  • Title: Remit Advice Identifier
    Maximum Length: 150
    Additional unique identifier for a separate remittance advice.
  • Title: Remit Advice Identifier
    Maximum Length: 150
    Additional unique identifier for separate remittance advice.
  • Title: Remit Advice Identifier
    Maximum Length: 150
    Remittance advice identifier used for separate remittance advice processing.
  • Title: Remit Advice Identifier
    Maximum Length: 150
    Additional unique identifier for a separate remittance advice.
  • Title: Remit Advice Identifier
    Maximum Length: 150
    Additional remittance advice identifier used for separate remittance advice processing.
  • Title: Remit Advice Identifier Type
    Read Only: true
    Maximum Length: 80
    Type of remittance advice identifier assigned to the digital payment account.
  • Title: Start Date
    The date when the relationship between the payment instrument and the payer or payee becomes active in the payment instrument assignment.
  • Title: Straight Through Processing
    Read Only: true
    Maximum Length: 1
    Indicates whether straight through processing is enabled for the digital payment account.
  • Title: Token
    Maximum Length: 150
    Substitute identifier of the digital payment account.
  • Title: Token Type
    Read Only: true
    Maximum Length: 80
    Type of token assigned to the digital payment account.
  • Title: Card Program
    Maximum Length: 100
    Virtual card program associated with the digital payment account.
Back to Top