Forms & Payments Implementation · Week 4 · 3 questions
Select the best answer for each question then submit to see your score.
Question 1 of 3
When implementing a new payment write-back for a PMS, what is the first step before writing any code?
AEnable the payment capability flag in WAM for a test office
BCreate a feasibility document mapping Weave payment fields to PMS fields and documenting constraints
CImplement the payment write-back RPC in the SyncApp integration code
DSet up Grafana monitoring alerts for the new integration
Question 2 of 3
In the payment write-back Grafana dashboard, what does the integration team track — payment counts or attempt counts?
APayment counts — each successful payment is counted once
BAttempt counts — each retry of a failed write-back is stored and counted separately
CBoth — separate dashboards for counts and attempts
DNeither — the Grafana dashboard only shows latency, not counts
Question 3 of 3
Why is provider selection important in payment write-backs?
AWeave requires a provider to be selected to calculate the correct payment tax rate
BSome PMS vendors mandate a provider value when creating invoices, and offices need it for their financial ledger to show which provider performed the procedure
CProvider selection determines which bank account the payment is deposited to
DIt is only cosmetic — provider selection has no functional impact on write-backs