Retry Recurring Charge

POST 
/api/v1_0/payments/recurring/retry

Retry a declined recurring charge with the same transaction identifier, which rules out charging the customer twice. Do not resend the charge through Register Payment - that creates a new transaction.

Rules:

• only a charge declined with INSUFFICIENT_FUNDS, LIMIT_EXCEEDED, SYSTEM_ERROR, GENERAL_ERROR or ISS_OUTOFSERVICE can be retried,
• at most 3 retries within 5 minutes of creating the original charge; after that create a new charge,
• the recurring payment must still be active and the amount must pass the same checks as the original charge.

HTTP 200 means the retry reached BLIK: retry.status is pending (the result arrives as for a charge - IPN on success, expired status on decline) or failed (BLIK rejected the retry immediately, code in retry.error). HTTP 400 means the retry is not allowed and nothing was sent to BLIK; the reason is in errors.retry (PAYMENT_NOT_DECLINED, DECLINE_NOT_RETRYABLE with the decline code in errors.decline_reason, RETRY_LIMIT_REACHED, RETRY_WINDOW_EXPIRED, ALIAS_NOT_AVAILABLE, RECURRING_NOT_ENABLED, PAYMENT_NOT_FOUND, Service unavailable) or in a field key (errors.transaction_id, errors.recurring_alias, errors.value).

Rate limit: 30 requests per minute.

Checksum Generation

sha256({service}|{secret}|{transaction_id})

Request

Responses

200

Retry sent to BLIK

400

Retry not allowed - nothing was sent to BLIK