Skip to main content
Repay is a payments technology company. Gr4vy integrates with Repay’s Payrazr gateway to process card payments for merchants in the United States.

​
Setup

Repay doesn’t offer self-service sign-up. Speak to your Repay account manager to request sandbox credentials for the Payrazr gateway.

​
Connector configuration

After setting up your Repay connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:
  • Using Flow - Configure Repay as the target connector in Flow to automatically route card transactions to this connector
  • Using the API - Explicitly set the payment_service_id parameter to the Repay connector ID when creating transactions. This overrides any Flow routing rules.
The connector ID can be found in the dashboard under Connections -> Configured connections.

​
Credentials

Configure the following credentials in the Gr4vy dashboard, which are provided by your Repay account manager:
  • API Username - Your Payrazr API username
  • API Password - Your Payrazr API password
  • ZID - Your Payrazr merchant location identifier

​
Capabilities

​
Supported countries

​
Supported currencies

​
Level 2 and 3 data

Cart items sent on a transaction are forwarded to Payrazr as Level 3 line item details. Commercial and purchasing cards can use this data to qualify for lower interchange rates, though whether a given transaction qualifies is determined by the card scheme and your acquirer, not by Gr4vy.

​
Storing cards

Storing a card with Repay creates a customer record in Payrazr, which requires a state on the billing address. Gr4vy sends the buyer’s state_code, so include it in ISO 3166-2 format, for example US-NY.
A state name on its own isn’t enough. Without state_code, Repay rejects the request with a generic The request is invalid. error that doesn’t identify the address as the cause. This affects storing a card, charging a stored card, and recurring payments.

​
Limitations

  • Only Apple Pay is supported - Of the digital wallets, Payrazr only supports Apple Pay. Attempting to pay with Google Pay or another wallet returns an unsupported_payment_method error.
  • Zero-amount authorizations require card details - Verifying a card without charging it only works when card details are submitted directly. It isn’t supported when charging a stored token.
  • Single recurring indicator - Repay doesn’t distinguish the first customer-initiated transaction in a recurring series from later merchant-initiated ones. Gr4vy flags the whole series as recurring using a single indicator.
  • Limited address verification - Only the billing address line and postal code are sent for AVS checks. City, state, and country aren’t included.
  • No shipping address - The Payrazr API has no field for shipping details, so shipping information isn’t sent.
This is a closed-loop connector. Some failover scenarios are limited. For details, see Open-loop versus closed-loop.

​
Integration

To accept card payments with Repay, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which routes the payment to your configured Repay connection based on your Flow rules or explicit payment_service_id parameter.

​
Testing

Repay’s sandbox accepts the following test card numbers. Use any future expiry date and any 3-digit CVV (4 digits for American Express). Any correctly formatted transaction over $1 that doesn’t match one of the triggers below is approved. To simulate a decline, submit the trigger amount as the transaction amount, or pass the trigger value in the cardholder name.