Subscriptions & recurring payments — found from sitemap — Paysera

Cited by

Facts read from this source

• Recurring billing API Report an error

  “The Paysera Recurring Billing API enables automated recurring payments using saved payment tokens. Create payment requests, authorize payments, and manage notifications programmatically.”

• API version Report an error

  “Version: 1.0.0”

• Base urls Report an error

  “Checkout API: https://checkout-eu-a.paysera.com/checkout/rest/v1 Notification API: https://checkout-eu-a.paysera.com/notification/rest/v1”

• Auth method Report an error

  “Most endpoints require MAC (Message Authentication Code) authentication. Some public endpoints do not require authentication.”

• Endpoints payment request Report an error

  “/payment-requests POST ✓ Yes Create a new payment request”

• Public info endpoint Report an error

  “/payment-requests/{id}/public-info GET ❌ No Get public payment information”

• Authorize endpoint Report an error

  “/payment-requests/{id}/authorize PUT ✓ Yes Authorize payment with token”

• Notifications endpoints Report an error

  “/notifications GET ✓ Yes Get all notifications with filtering”

• Initial payment requirements Report an error

  “Provide accept_url, cancel_url, and callback_url (all required) Set token_strategy: "required" to obtain a payment token”

• Token delivery Report an error

  “After successful capture, you receive an issued_token on the Payment Request, delivered via the callback notification at data.payment_request.issued_token”

• Recurring payments Report an error

  “No user interaction required - payment is automatically captured during authorisation”

• Payment statuses Report an error

  “new - Payment request created, awaiting customer payment processing - Payment is being processed authorized - Payment authorized, ready for capture captured - Payment successfully completed and funds captured canceled - Payment was canceled or refunded instantly_refunded - Payment was immediately refunded”

• Notification statuses Report an error

  “new - Notification created, not yet processed read - Notification has been marked as processed”

• Rate limiting Report an error

  “The API implements rate limiting to ensure service stability. If you exceed the rate limit, you will receive a 429 Too Many Requests response.”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.

Scores citing this record

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