Charge for Registering a Financing Statement

[sandrajoandaniel]

Story: As the Registrar, we want to charge a fee for submitting a Financing Statement so that costs are recouped.

Acceptance Criteria:

• Basic User
• Premium User

Dependencies

• Authorization API: Account ID, Account Type or payment method
• Payment API: Credit Card Flow, and later, the "Draw down" account.

Question:

• What do we do if the payment system is down?
• No payment scenario: Insufficient funds or ??? What do we do?

[colinanderson-cgi]

603 is an integration exercise that is only nominally dependent on regulation insofar that regulation dictates that a payment must be made for registering a financing statement. For the purposes of grabbing the account ID, we can pull Account ID from Account Info in the JWT token

Ref: General Regulations Division 3 - Fees, Section 52,53,54

[colinanderson-cgi]

• What do we do if the payment system is down?
• No payment scenario: Insufficient funds or ??? What do we do?

This came up a lot when I did Payment Card Interface work a long time ago. What is standard, and is accepted in the PCI industry, is to pre-auth the card, or charge the card FIRST or do some sort of credit from an account before you let the user perform the function. Pre-auth should be do-able and it exposes two things, the validity of the credit and whether payment auth is up or down.

Another strategy I have seen used is that all payment gateway systems have a "test card" that can be called at will to verify functionality, run the "test card" first. This should not clause any appreciable incremental system load