Subscriptions & recurring payments — found from sitemap — Paysera

Cited by

Facts read from this source

• Recurring billing definition Report an error

  “Recurring billing is used to charge money without user interaction. For example, to charge subsequent amounts from a user's credit card for monthly subscriptions.”

• Token reuse Report an error

  “After obtaining a token from the first payment, you can reuse the same token for all future charges until it expires.”

• Prerequisites token strategy Report an error

  “Complete the standard payment flow with token_strategy: "required"”

• Create payment request endpoint Report an error

  “Create a new payment request via POST to /checkout/rest/v1/payment-requests”

• Authorize endpoint Report an error

  “Authorize the payment using the stored token via PUT to /checkout/rest/v1/payment-requests/{id}/authorize”

• Automatic capture Report an error

  “The payment is automatically captured during the authorisation process. No additional confirmation is needed.”

• Notification flow Report an error

  “Paysera sends a POST request to your callback_url with a notification_id parameter.”

• Notification endpoints Report an error

  “Get notification: GET /notification/rest/v1/notifications/{id} Mark as read: PUT /notification/rest/v1/notifications/{id}/read”

• Notification retry Report an error

  “You must mark notifications as read. If you don't, Paysera will retry the callback multiple times until it's marked as read.”

• API host Report an error

  “Host: checkout-eu-a.paysera.com”

• Authentication Report an error

  “Authentication: All requests require MAC authentication headers.”

• Zero amount token flow Report an error

  “You can also obtain a recurring billing token without actually transferring any funds from the customer. This is useful when you only need to register a payment method for future automatic charges (for example, a free trial that converts to a paid subscription later).”

• Refund on capture Report an error

  “When refund_on_capture is true, the captured amount is automatically refunded back to the customer and the Payment Request ends in the canceled status, but a recurring billing token is still issued.”

• Token issued notification event Report an error

  “The notification event is payment_request.checkout_token_issued (not payment_request.captured).”

• Issued token usable Report an error

  “The issued_token field is still present on the Payment Request and can be used for subsequent recurring charges exactly like a token from a normal capture.”

• Token security Report an error

  “Store tokens encrypted in your database Never expose tokens in client-side code Use HTTPS for all API communications Implement proper access controls”

• Token validity Report an error

  “Token validity: Tokens remain valid until customer revokes them or the payment card expires”

Scores citing this record

• The Compliance Officer Subscriptions & recurring payments
• The Compliance Officer European sovereignty
• The E-Commerce Lead Checkout, SCA & fraud
• The E-Commerce Lead Subscriptions & recurring payments
• The E-Commerce Lead Settlement, reconciliation & API
• The Payments Engineer Subscriptions & recurring payments
• The Finance Lead Subscriptions & recurring payments
• The Skeptic Subscriptions & recurring payments
• The SaaS Founder Subscriptions & recurring payments