Skip to main content
Users can link debit or credit cards to their Paywint profile so they can fund payments or receive withdrawals.
Paywint handles all sensitive card data through secure, time-limited links, ensuring that no card information ever touches your servers. The card flow is straightforward:
  • Add Card — Create a secure link for the user to add a new card
  • Update Card — Only required when Paywint asks the user to complete missing information or verification steps

​
Card Features

You can:
  • Provide users a secure link to add a card
  • Allow required updates when Paywint flags missing steps
  • Retrieve card details and verification requirements
  • List all cards for a user
  • Delete a card when needed
Cards may be used for:
  • Funding payments
  • Receiving withdrawals (when configured for that purpose)

​
Available APIs

Add Card

Generate a secure link for adding a new card.

Update Card

Generate a secure link only when the user must complete required steps.

Get Card

Retrieve card details and required action flags.

List Cards

Fetch all cards linked to a user.

Delete Card

Remove a card from the user’s account.

​
How the Card Flow Works

1

1. Generate a secure link

Call Add Card to create a secure link for adding a new card.
The link is valid for 30 minutes and must be opened immediately.
2

2. User enters card information

The user adds their card on the Paywint-hosted page.
Sensitive card details never go through your platform.
3

3. Card becomes available

Once completed, the card is ready for payments or withdrawals based on its purpose.

​
When the User Must Update Their Card

The Update Card flow is not for general editing.
A user only needs to update a card when Paywint determines that:
  • Required card images are missing
  • Additional verification is needed for withdrawals
  • Payment confirmation is required before new payments
  • A security or compliance check requires the user to re-authenticate the card
In these cases, Paywint temporarily restricts the card until the user completes the update link. Call the update endpoint to generate a secure link, and the user finishes the required step in the Paywint-hosted form.

​
Card Status Flags

When retrieving a card, these flags indicate required user actions:
FlagMeaning
card_images_requiredUser must upload images before the card is usable.
withdrawal_confirm_requiredAdditional setup needed for withdrawal capability.
payment_confirm_requiredExtra verification required before processing new payments.
is_limitedUser reached their daily spending limit (withdrawals still allowed).
If any of the first three flags are true, direct the user through the Update Card flow.

​
Best Practices

  • Always open add/update secure links immediately after generation
  • Do not reuse expired links (valid for 30 minutes)
  • Use card flags to determine when an update is required
  • Display only masked card details (e.g., last 4 digits)