Service - CommerceAccounting Customer Payment
Revision as of 14:35, 23 January 2026 by Sven the Barbarian (talk | contribs) (Created page with "= Overview = Handle payments by customers. = Repository = ... = Object Schemas = ; Additional Information: Per Service Schemas <syntaxhighlight lang="JavaScript"> { objectType: "comAccCustomerPaymentLink", canDelete: false, belongTo: { serviceTag: "ComAccLink", objectType: "comAccLink" }, addOnDataStructure: [], storageResources: { "dynamo": { "storageType": "dynamoDB", "tableName": "comAccCustomerPaymentLink", } }, fieldNames: { //...")
Overview
Handle payments by customers.
Repository
...
Object Schemas
- Additional Information
- Per Service Schemas
{
objectType: "comAccCustomerPaymentLink",
canDelete: false,
belongTo: {
serviceTag: "ComAccLink",
objectType: "comAccLink"
},
addOnDataStructure: [],
storageResources: {
"dynamo": {
"storageType": "dynamoDB",
"tableName": "comAccCustomerPaymentLink",
}
},
fieldNames: {
// probably have two dynamo tables, one identified by purchaseId, one by journalId
},
identifiers: [
{
// see above note
}
]
}
- maintains a link between customerPaymentId and journalIds, so can adjust if changes made to payment
Relationships
...
flowSchemas
customerPaymentCreated
- when creating a customer payment add journal entries
customerPaymentChange
- make adjustment to journal entries
- need to check for locked records