Update Payment Preferences
Description
Payers can update their payment preferences through the Update Payment Preference service. Payer has an option to either update their payment preference at the account level or update the payment preferences at the Biller level. Updating at an account level will impact all the bills linked to the same Biller. Updating at a bill level will only impact a single bill. This flow describes the process to update the account-level payment preferences. These updated preferences are stored locally at Bill Pay Accelerator of the PI and acted upon on receiving payment requests.
Payment Preference Update Scenarios
- Billing Account is already linked and autopay is "Off". Payer changes the autopay setting to "On". This change will Not affect the received pending bills.
- Billing Account is already linked and autopay is "On". Payer changes the autopay preferences. This change will affect the received pending bills.
- Billing Account is already linked and autopay is "On". Payer changes the autopay setting to "Off". This change will Not affect the received pending bills.
![06-Update Payment Preferences.png 1128](https://files.readme.io/861c7fc-06-Update_Payment_Preferences.png)
The following steps demonstrate the Update Payment Preferences user flow:
![](https://files.readme.io/9bff313-Group_1.png)
PI uses
Link Retrieval API
to fetch the Payer's linked accounts.
PI should show the details page with list of all the accounts linked for a Biller.
![](https://files.readme.io/1537799-101.png)
![](https://files.readme.io/bcea82a-Group_2.png)
Payer selects an account with autopay "Off".
![](https://files.readme.io/db60b24-102_autopay_on.png)
![](https://files.readme.io/43604c2-Group_3.png)
Payer changes autopay setting to "On".
![](https://files.readme.io/d27966f-103.png)
![](https://files.readme.io/68af3fd-Group_4.png)
PI may use same form as used during link request process.
Payer needs to add payment method, select amount and date prefernces.
![](https://files.readme.io/0a2c66c-104.png)
![](https://files.readme.io/e2da30f-Group_5.png)
PI may notify Payer that current feature will only apply to the newly generated bills.
![](https://files.readme.io/3e4544f-105.png)
![](https://files.readme.io/74677ed-Group_6.png)
Maintain(Update) Link API
will submit the requested changes.
Bill Pay Accelerator stores this information locally in the PI
database and updates the payment request service with the changes.
Mastercard Bill Pay Exchange will not be called in this flow.
![](https://files.readme.io/4681eb0-106.png)
![](https://files.readme.io/93c620b-Group_7.png)
This flows depicts the Payer changing autopay preferences from "On" to "Off"
![](https://files.readme.io/0770a40-107.png)
![](https://files.readme.io/ae214cc-Group_8.png)
Payer may either change autopay to "Off" or revise existing autopay preferences.
![](https://files.readme.io/d5e9eda-108.png)
![](https://files.readme.io/2a9834c-Group_9.png)
Payer changes autopay to "Off".
![](https://files.readme.io/3009d97-109.png)
![](https://files.readme.io/2152bda-Group_10.png)
PI may notify Payer that current feature will only apply to the newly generated bills.
![](https://files.readme.io/e24c255-110.png)
![](https://files.readme.io/d60175e-Group_11.png)
Maintain(Update) Link API will submit the requested changes. Bill Pay
Accelerator stores this information locally in the PI database and
updates the payment request service with the changes.
Mastercard Bill Pay Exchange will not be called in this flow.
![](https://files.readme.io/6b25fd8-112.png)
Updated over 2 years ago