How payment source updates work for PSPs

View as Markdown (opens in a new tab)

Install AI tools

Our plugin gives your assistant up-to-date guidance for payments and login. Full instructions

Claude Code

Run both commands, in order.

claude plugin marketplace add vippsas/agent-toolkit
claude plugin install vipps@agent-toolkit

Cursor

Open Settings, then Plugins.

Add vippsas/agent-toolkit as a plugin marketplace, then install the "vipps" plugin.

Codex

See the Codex plugin docs at developers.openai.com/codex.

Add vippsas/agent-toolkit as a plugin marketplace, then install the "vipps" plugin.

Any editor

No plugin needed. Paste this into your assistant.

Read https://developer.vippsmobilepay.com/llms.txt for the Vipps MobilePay developer documentation.

A walkthrough of what happens when a user changes the card attached to an existing agreement.

Details

When a user changes their card on an existing agreement in the app, Vipps MobilePay sends a zero-amount CIT to the PSP's cardCallbackUrl to verify the new card. The flow is identical to the card callback in agreement sign-up — no action is needed from the merchant's website.

Sequence diagram

PSP merchant payment source update flow

100%

1. User initiates a payment source change on their agreement with Vipps MobilePay.
2. Vipps MobilePay posts the new card token to the PSP's cardCallbackUrl.
3. PSP processes a verification payment using the new token.
4. PSP returns 200 OK to Vipps MobilePay.
5. Vipps MobilePay notifies the user that the update was successful.

More information

For technical details, see the Recurring PSP API guide.