Allocate a Suspended Payment to an Account
post
/bcws/webresources/v1.0/payments/suspense/allocate
Allocates a suspended payment to the specified account.
Request
Query Parameters
-
validate(required): string
Whether to validate that the account has an open bill that is due. When validate=openBills, it checks if the account has any open due bills. For any other value, validation is skipped.
Supported Media Types
- application/xml
- application/json
Information for allocating the suspended payment. The schema payload should contain the following:
- The event resource associated with the suspended account
- The amount to allocate to the target account
- The target account's currency
- The total amount to allocate from suspense
- (Optional) The bill items along with the amount to allocate to each one in case of manual allocation of items
Root Schema : schema
Type:
Show Source
object
-
details: array
details
The list of details associated with the recycled payment.
-
effectiveDate(required): string
(date-time)
The date and time the recycled payment took effect.
-
eventRef: object
ResourceRef
-
extension: object
extension
The extended attributes.
-
notes: object
Notes
-
unallocatedSuspendedAmount(required): number
The amount of the original payment that hasn't been allocated.
Nested Schema : details
Type:
array
The list of details associated with the recycled payment.
Show Source
-
Array of:
object Details
The offer details.
Nested Schema : ResourceRef
Type:
Show Source
object
-
id(required): string
The ID.
-
uri: string
The Uniform Resource Identifier (URI) associated with the resource.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Notes
Type:
Show Source
object
-
accountId(required): string
The ID of the account associated with the note.
-
amount: number
The amount associated with the note. It can be a payment amount, adjustment amount, or so on.
-
billId: string
The ID of the bill associated with the note.
-
billUnitId: string
The ID of the bill unit associated with the note.
-
closedDate: string
(date-time)
The date and time the note was resolved.
-
comments: array
comments
The list of comments associated with the note.
-
count: integer
(int32)
The number of comments associated with the note.
-
domainId: integer
(int32)
The domain ID associated with the note.
-
effectiveDate: string
(date-time)
The date and time the comment was posted.
-
eventId: string
The ID of the event associated with the note.
-
extension: object
extension
The extended attributes.
-
header: string
The header associated with the note.
-
id: string
The ID.
-
itemId: string
The ID of the item associated with the note.
-
reasonId: integer
(int32)
The reason ID associated with the note. Possible values are stored in /config/reason_code_scope objects. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the reasons.locale file.
-
serviceId: string
The service ID associated with the note.
-
status: number
The note's status: not set (100), resolved (101), or unresolved (102). The default value is 102.
-
subType: integer
(int32)
The note's subtype. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
-
type: integer
(int32)
The note's type. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
Nested Schema : Details
Type:
object
The offer details.
Show Source
-
balanceImpactResource(required): string
The resource that represents the balance impact of the offer.
-
fixedAmount: number
(float)
The fixed amount of the offer.
-
fixedPriceTag(required): string
The fixed price tag of the offer.
-
scaledAmount: number
(float)
The scaled amount of the offer.
-
scaledPriceTag(required): string
The scaled price tag of the offer.
Nested Schema : comments
Type:
array
The list of comments associated with the note.
Show Source
-
Array of:
object Comments
The list of comments associated with the note.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Comments
Type:
object
The list of comments associated with the note.
Show Source
-
comment(required): string
The comment.
-
csrAccountId: string
The CSR's account ID.
-
csrFirstName: string
The CSR's first name.
-
csrLastName: string
The CSR's last name.
-
csrLoginId: string
The login ID associated with the CSR.
-
entryDate: string
(date-time)
The date and time the comment was entered by the CSR.
-
externalUser: string
The external user.
-
trackingId: string
The tracking ID.
Information for allocating the suspended payment. The schema payload should contain the following:
- The event resource associated with the suspended account
- The amount to allocate to the target account
- The target account's currency
- The total amount to allocate from suspense
- (Optional) The bill items along with the amount to allocate to each one in case of manual allocation of items
Root Schema : schema
Type:
Show Source
object
-
details: array
details
The list of details associated with the recycled payment.
-
effectiveDate(required): string
(date-time)
The date and time the recycled payment took effect.
-
eventRef: object
ResourceRef
-
extension: object
extension
The extended attributes.
-
notes: object
Notes
-
unallocatedSuspendedAmount(required): number
The amount of the original payment that hasn't been allocated.
Nested Schema : details
Type:
array
The list of details associated with the recycled payment.
Show Source
-
Array of:
object Details
The offer details.
Nested Schema : ResourceRef
Type:
Show Source
object
-
id(required): string
The ID.
-
uri: string
The Uniform Resource Identifier (URI) associated with the resource.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Notes
Type:
Show Source
object
-
accountId(required): string
The ID of the account associated with the note.
-
amount: number
The amount associated with the note. It can be a payment amount, adjustment amount, or so on.
-
billId: string
The ID of the bill associated with the note.
-
billUnitId: string
The ID of the bill unit associated with the note.
-
closedDate: string
(date-time)
The date and time the note was resolved.
-
comments: array
comments
The list of comments associated with the note.
-
count: integer
(int32)
The number of comments associated with the note.
-
domainId: integer
(int32)
The domain ID associated with the note.
-
effectiveDate: string
(date-time)
The date and time the comment was posted.
-
eventId: string
The ID of the event associated with the note.
-
extension: object
extension
The extended attributes.
-
header: string
The header associated with the note.
-
id: string
The ID.
-
itemId: string
The ID of the item associated with the note.
-
reasonId: integer
(int32)
The reason ID associated with the note. Possible values are stored in /config/reason_code_scope objects. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the reasons.locale file.
-
serviceId: string
The service ID associated with the note.
-
status: number
The note's status: not set (100), resolved (101), or unresolved (102). The default value is 102.
-
subType: integer
(int32)
The note's subtype. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
-
type: integer
(int32)
The note's type. Possible values are stored in the /config/note_type object. See Localizing and Customizing Strings in BRM Developer's Guide for information about how to customize these values using the note.locale file.
Nested Schema : Details
Type:
object
The offer details.
Show Source
-
balanceImpactResource(required): string
The resource that represents the balance impact of the offer.
-
fixedAmount: number
(float)
The fixed amount of the offer.
-
fixedPriceTag(required): string
The fixed price tag of the offer.
-
scaledAmount: number
(float)
The scaled amount of the offer.
-
scaledPriceTag(required): string
The scaled price tag of the offer.
Nested Schema : comments
Type:
array
The list of comments associated with the note.
Show Source
-
Array of:
object Comments
The list of comments associated with the note.
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : Comments
Type:
object
The list of comments associated with the note.
Show Source
-
comment(required): string
The comment.
-
csrAccountId: string
The CSR's account ID.
-
csrFirstName: string
The CSR's first name.
-
csrLastName: string
The CSR's last name.
-
csrLoginId: string
The login ID associated with the CSR.
-
entryDate: string
(date-time)
The date and time the comment was entered by the CSR.
-
externalUser: string
The external user.
-
trackingId: string
The tracking ID.
Response
Supported Media Types
- application/xml
- application/json
201 Response
The suspended payment was successfully allocated to the account.
Root Schema : resource
Type:
Show Source
object
-
extension: object
extension
The extended attributes.
-
reference(required): object
ResourceRef
Nested Schema : extension
Type:
object
The extended attributes.
Nested Schema : ResourceRef
Type:
Show Source
object
-
id(required): string
The ID.
-
uri: string
The Uniform Resource Identifier (URI) associated with the resource.
400 Response
The request isn't valid.
500 Response
An internal server error occurred.
Examples
This example shows how to allocate a suspended payment to an account by submitting a POST request on the REST resource using cURL. For more information about cURL, see "Use cURL".
cURL Command
curl -X POST 'http://hostname:port/bcws/webresources/version/payments/suspense/allocate' -H 'content-type: application/json' -d @allocateSupendedPayment.json
where:
- hostname is the URL for the Billing Care REST server.
- port is the port for the Billing Care REST server.
- version is the version of the API you're using, such as v1.0.
- allocateSupendedPayment.json is the JSON file that specifies the allocation details.
Example of Request Body
This example shows the contents of the allocateSupendedPayment.json file sent as the request body.
{
"eventRef": {
"id": "0.0.0.1+-event-billing-payment-cash+328270191589064123"
},
"details": [
{
"accountRef": {
"id": "0.0.0.1+-account+181438"
},
"currency": 840,
"reasonId": "11",
"domainId": 5,
"billItems": [
{
"itemRef": {
"id": "0.0.0.1+-item-cycle_forward+260691"
},
"amount": -50
}
],
"totalAmount": 50
}
],
"unallocatedSuspendedAmount": 50
}
Example of Response Body
This example shows the contents of the response body in JSON format.
{
"extension": null,
"reference": {
"id": "0.0.0.1+-event-billing-payment-cash+328270191589063256",
"uri": "http://hostname:port/bcws/webresources/v1.0/payments/0.0.0.1+-event-billing-payment-cash+328270191589063256"
}
}