Setup
BlueSnap provides a self-service sign-up for a sandbox account. To sign up for an account, visit the BlueSnap sign-up page and fill in the required details.Credentials
When setting up BlueSnap in the dashboard, configure the following credentials:- API User Key - Your BlueSnap API User Key
- API Password - Your BlueSnap API Password
- Webhook Security Header - Optional security header for webhook validation
- Merchant ID (MID) - Required if Surcharging is enabled, optional otherwise
- Enable Surcharge - Automatically calculate and apply a surcharge to transactions using BlueSnap’s surcharge feature. The account must already have surcharging enabled with BlueSnap.
Gated features
Some BlueSnap features need to be enabled by their support team before you can use or test them:- 3-D Secure - Requires activation on the account using the external 3DS server
- Digital wallets - Apple Pay and Google Pay must be enabled on the account
- Surcharge - surcharging needs to be enabled on your account by BlueSnap support
Connector configuration
After setting up your BlueSnap connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:- Using Flow - Configure BlueSnap as the target connector in Flow to automatically route card transactions to this connector
- Using the API - Explicitly set the
payment_service_idparameter to the BlueSnap connector ID when creating transactions. This overrides any Flow routing rules.
Surcharging
Surcharging is a feature enabled for the account, not the credential. Once BlueSnap’s support team activates it, all transactions with a non-zero amount require a surcharge token generated by BlueSnap to process. Make sure the credential in the Gr4vy dashboard is also marked with Enable Surcharge to match. The amount sent to Gr4vy should always be the raw amount, with no fees included. Gr4vy uses this raw amount to calculate the surcharge via BlueSnap’s own API (/surcharge/calculate, or /surcharge/calculate-prorated for partial captures),
generating a surcharge token and the fee amount to add before sending the total to
BlueSnap. For a full capture, the captured amount is expected to already equal the
authorized total (raw amount + surcharge), so it’s sent as-is without generating a new token
Capabilities
Supported countries
Supported currencies
Integration
To accept card payments with BlueSnap, 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
payment_service_id parameter.
Testing
For testing in sandbox environments, you can use standard test card numbers. BlueSnap supports industry-standard test cards for simulating different transaction scenarios: Successful transactions:- Visa:
4111 1111 1111 1111 - Mastercard:
5555 5555 5555 4444 - American Express:
3782 822463 10005