| Product | Summary |
| Digital Payments |
|
Update Stored Payment Methods API
A new
PUT /payment-methods/{payment_method_id} endpoint allows you to modify the details of a stored card or payment method without having to delete and re-vault it. You can seamlessly update the expiration_date and scheme transaction IDs, allowing you to maintain the same payment method ID for downstream references.
Why it matters:
When a stored card is reissued or its expiration date changes, merchants previously had to delete the record and vault a new one—losing the payment method ID and any downstream references. This endpoint lets merchants keep the same payment method ID while refreshing key details, reducing churn in buyer records and preserving continuity for recurring billing and scheme transaction history.
Fields you can update:
-
expiration_date: The new expiration date for the card (for example,12/30). -
scheme_transaction_id: A scheme transaction identifier to associate with the payment method. -
scheme_transaction_id_scheme: The card scheme associated with thescheme_transaction_id(for example,visa,mastercard).
Notes:
- Setting
scheme_transaction_idtonullalso clearsscheme_transaction_id_scheme. - If
scheme_transaction_idis set andscheme_transaction_id_schemeare both omitted from the payload and previously unset, it defaults to the payment method’sscheme.
Gift Card Usage Data Tracking
For merchants utilising Qwikcilver gift cards, stored gift cards now track usage statistics, including
last_used_at and usage_count. You can append the sort_by=last_used_at or sort_by=cit_last_used_at parameters when calling GET /buyers/gift-cards to automatically surface the buyer's most recently used gift card.
Stored gift cards now track usage statistics, making it easier to determine which card to preselect at checkout or surface as the preferred option in your UI.