Branch management
Move a customer or a card between branches, and read the cards a branch holds.
changeCardBranch
Changes the branch of a debit card or customer accounts, including transferring multiple customers between branches. Returns old and new branch information and affected card counts.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
changeCardBranch › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
shadowCardNumberThe card being moved to another branch.
targetBranchCodeThe branch the card is moved to. There is no current-branch field on this operation — the card's branch is read rather than asserted.
changeCardBranch › Responses
Success
isSuccessWhether the operation did what it was asked to. A false here arrives with HTTP 200, so it has to be read rather than inferred from the status.
oldBranchThe branch before the move.
newBranchThe branch after it.
changeCustomerBranch
Changes the branch for a customer and updates all associated cards. Returns the number of changed cards, list of shadow card numbers, old branch, and new branch.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
changeCustomerBranch › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
customerNumberThe customer at the bank's core banking system, as a number. The platform stores it rather than issuing it, so it comes from the core.
targetBranchCodeThe branch to move the card or customer to.
changeCustomerBranch › Responses
Success
oldBranchThe branch before the move.
newBranchThe branch after it.
changedCardCountHow many cards the operation changed.
listOfShadowCardNumbersThe cards the operation acted on.
transferBranchCustomer
Transfers a customer to a different branch. Updates the branch assignment for a customer in the debit channel system.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
transferBranchCustomer › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
currentBranchCodeThe branch the customers are moved from. Refused when it is the same as targetBranchCode — a transfer to the branch already held is an error here, not a no-op.
targetBranchCodeThe branch the customers are moved to.
listOfPersonIdWhich customers to move. Checked for presence, not for contents.
transferBranchCustomer › Responses
Success
oldBranchThe branch before the move.
newBranchThe branch after it.
changedCardCountHow many cards the operation changed.
listOfShadowCardNumbersThe cards the operation acted on.
getDebitCustomerLisfOfBranch
Retrieves the list of debit customers for a given branch. Uses channel information and branch code to return customer OID list.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getDebitCustomerLisfOfBranch › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
branchCodeRequired in practice — Branch whose customers are listed. Not validated — the facade's null check cannot fail, because the field is a bare int, so an omitted value arrives as zero, matches no branch and comes back as an empty list rather than a refusal.
getDebitCustomerLisfOfBranch › Responses
Success
customerOid